Win a copy of Head First Android this week in the Android forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Rob Spoor
  • Bear Bibeault
Saloon Keepers:
  • Jesse Silverman
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • Al Hobbs
  • salvin francis

Regarding Base64 emails

 
Ranch Hand
Posts: 223
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,

I have created one java mail application. i have sent one zip attachment e-mail to my client e-mail address.
but their mail server is not able retrive the mail.

but when i send this zip attachment mail to other e-mail id's (other server like yahoo, hotmail...etc), it is working perfectly.

please tell your suggestions.

when i check the attachment mail property. it looks like
Content-Transfer-Encoding: base64

Is base64 is common for zip attachment. But I did not encode. Please advise.

Thanking You.
Regards
Edward
 
Sheriff
Posts: 22508
122
Eclipse IDE Spring VI Editor Chrome Java Windows
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
You probably didn't know this, but every email is actually plain text, even RTF emails and HTML emails. It has different sections (e.g. the headers, the body, the attachments), and some of these sections can be encoded. This encoding is a means for putting non-plain text in the plain text email. Base64 is the most common way for attachments to be encoded.

When a client opens an email, it checks all sections, and decodes where necessary. Then it displays all sections as needed.
 
Edward Durai
Ranch Hand
Posts: 223
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks for your reply.

Actually In my java mail application, at run time, I have created zip files and send to particular e-mail id.

It's working fine. But in particular e-mail id's not working.

But without using Javamail API (manually), that is manually i have sent one zip attachement to the same e-mail id. It's working perfectly.

But In JavaMail API, zip attachment is not going to that particular id.

I have asked to that mail server programmers, they told me, they got some errors, when receiving my e-mails.

But other e-mails are working. When I check the other e-mails, the mail properties looks like


Content-Type: application/zip; name=onshore_342_onshore_934_25.zip
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename=onshore_342_onshore_934_25.zip


So please adivise.

Thanking You.
 
Rancher
Posts: 43027
76
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

they got some errors


What errors are those, exactly?
 
Edward Durai
Ranch Hand
Posts: 223
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

Actually their mail have attached below

"The cause of the problems you are encountering while sending the zip.files attached to the emails have been located by our Amos Technical Experts.

The emails are not being blocked, but during storage of the attachment within our Amos database the system is generating errors:



I 20080422 133121 3536 SMTP incoming from 212.165.122.17
T 20080422 133121 3536 EHLO relay1.station12.com
T 20080422 133121 3536 MAIL FROM:<onshore@tcslgroup.net>
T 20080422 133121 3536 RCPT TO:<vrm@amosconnect.com>
T 20080422 133134 3536 DATA
E 20080422 133134 3536 Unable to save message in database
T 20080422 133134 3536 QUIT



This is a bug within our system which needs to be solved by our Amos Development Department".

Thanking You.
 
Ulf Dittmer
Rancher
Posts: 43027
76
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Sounds like the receiving side is aware of the problem, and -hopefully- working to fix it.
 
reply
    Bookmark Topic Watch Topic
  • New Topic