Topic: two problems with email formatting

[aredman]

I have been running into two problems with the email that is being sent out from my e-smith server. The first one is, some mail that is sent out (particularly ones to and aol account) get bounced back with the following message:

*****************
 > Hi. This is the qmail-send program at xxx.org
> I'm afraid I wasn't able to deliver your message to the following
addresses.
> This is a permanent error; I've given up. Sorry it didn't work out.
>
> <XXX@aol.com>:
> 205.188.158.121 failed after I sent the message.
> Remote host said: 554-: (RLY:FA)
http://postmaster.info.aol.com/errors/554rlyfa.html
> 554 TRANSACTION FAILED
>
> --- Below this line is a copy of the message
***************
when I check the link that is provided it tells me:

**********
All or part of the from address contained in your message is missing or improperly formatted.

SOLUTION:

Please correct the message "From: address" sent in your SMTP transaction. The from address is typically formatted as myEmailHere@my-Domain.com. You may need to contact your ISP or server administrator for additional assistance.
***********

Is there a way to fix this so I dont get this error?

The second problem is, when some mail gets sent to mail clients that are web-based, The message does not get sent correclty. Instead of the nice looking one that gets sent out, themessage shows up with all the MIME headers inline with the text and any attachments apear as a code block at the end of the message. Is there a reason that this occurs and a way to change it so the messages show up properly on the receiving end?

thanks in advance

[boringgit]

Please correct the message "From: address" sent in your SMTP transaction. The from address is typically formatted as myEmailHere@my-Domain.com. You may need to contact your ISP or server administrator for additional assistance.
***********

Is there a way to fix this so I dont get this error?

The from address is set in the senders mail client. Take a look at their PC - my guess is that they have it set incorrectly

The second problem is, when some mail gets sent to mail clients that are web-based, The message does not get sent correclty. Instead of the nice looking one that gets sent out, themessage shows up with all the MIME headers inline with the text and any attachments apear as a code block at the end of the message. Is there a reason that this occurs and a way to change it so the messages show up properly on the receiving end?

I have rarely experienced this and would guess at a receiver config problem...

Try sending a mail to both the web client and a normal client and see if the normal client receives OK?

[aredman]

The from address is correct in the mail client, The first error occurs when anyone tries to email a person that has an aol.com email address.

As far as the second problem. The same person can send an email with recipients that have a web based email client and those that dont. The ones that dont, get the message just fine, The ones that have the web based client get it printed all out with the mime headers and everything

[boringgit]

Oh..  

Kinda dumb elimination still, but try another mail client?

Not a solution, but if the problem continues using an alternative package than you can rule out the client altogether.

(SME IMP webmail would qualify - assuming that the users in question are not using this when they experience their problems..)

[ed]

The second problem is, when some mail gets sent to mail clients that are web-based, The message does not get sent correclty. Instead of the nice looking one that gets sent out, themessage shows up with all the MIME headers inline with the text and any attachments apear as a code block at the end of the message. Is there a reason that this occurs and a way to change it so the messages show up properly on the receiving end?

I had this problem before. The web based client would treat the headers as email once it hit a particular header. I sent an email to myself at a web based account and figured out which header was causing it and was able to prevent that header from being inserted. The problem is most likely either the first header that shows up in the email on a web based client or the last one to be hidden in the source like it's supposed to be. Hopefully it will be one you can easily control.

HTH

- Ed

[aredman]

Ok, I verified that it is something with how wmail constructs the headers. NOw is there a way that I can go and modify the headers so this wont happen?

[Ed]

That would depend on which header it is. For me it was one that was created by Amavis-ng so I was easily able to prevent it from being inserted by editing the amavis conf file. By the way, after an Amavis upgrade this wasn't a problem for me anymore so the header is being inserted again with no problems.

- Ed