Community Discussions and Support
mercury sends mail in response to malformed from address

To clarify what I'm talking about line from the log:


T 20091219 122703 4b2aaa5d MAIL FROM: <Debora@http://profiles.yahoo.com/blog/WBC44CAC7DTOFYBLCD7ASLJCOM>

I think I have found the solution: I had 'honour request for transcript generation' ticked. If the message requests a transcript the from-address leads to an error.

I've disabled it now and  Have to wait and see ...

 

Both thanks for the response and  support.


 

&lt;p&gt;To clarify what I&#039;m talking about line from the log: &lt;/p&gt;&lt;p&gt; T 20091219 122703 4b2aaa5d MAIL FROM: &amp;lt;Debora@http://profiles.yahoo.com/blog/WBC44CAC7DTOFYBLCD7ASLJCOM&amp;gt; &lt;/p&gt;&lt;p&gt;I think I have found the solution: I had &#039;honour request for transcript generation&#039; ticked. If the message requests a transcript the from-address leads to an error.&lt;/p&gt;&lt;p&gt;I&#039;ve disabled it now and&amp;nbsp; Have to wait and see ...&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Both thanks for the response and&amp;nbsp; support.&lt;/p&gt;&lt;p&gt; &amp;nbsp;&lt;/p&gt;

I noticed the smtp client to send mail to an unresolved address on its own. I checked it and found that whenever a ( non-local) mail is recieved that has a from-address in the form of 'user@http://www.domain.nn/moretext' this happens. Mercury than truncates the address to 'www.d' .

Why does Mercury respond to a malformed from-address by trying to send an email? I am using version 4.5, and relaying is not allowed.

 Any suggestions or is this actually a bug?
 

&lt;p&gt;I noticed the smtp client to send mail to an unresolved address on its own. I checked it and found that whenever a ( non-local) mail is recieved that has a from-address in the form of &#039;user@http://www.domain.nn/moretext&#039; this happens. Mercury than truncates the address to &#039;www.d&#039; .&lt;/p&gt;&lt;p&gt;Why does Mercury respond to a malformed from-address by trying to send an email? I am using version 4.5, and relaying is not allowed.&lt;/p&gt;&lt;p&gt;&amp;nbsp;Any suggestions or is this actually a bug? &amp;nbsp;&lt;/p&gt;

Well, it's probably because you have it set to.

A bit more detail would help pinpoint the issue.

Can you post the raw headers of the message from the .cnm file?

Also some info about your setup, do you receive mail via MercD or MercS?

Your local domain name? Is the mail addressed to a valid local user?

Also some session logs of one of these messages passing through would be good [:)]

FWIW a from address should never look like that.

&lt;p&gt;Well, it&#039;s probably because you have it set to.&lt;/p&gt;&lt;p&gt;A bit more detail would help pinpoint the issue.&lt;/p&gt;&lt;p&gt;Can you post the raw headers of the message from the .cnm file?&lt;/p&gt;&lt;p&gt;Also some info about your setup, do you receive mail via MercD or MercS?&lt;/p&gt;&lt;p&gt;Your local domain name? Is the mail addressed to a valid local user? &lt;/p&gt;&lt;p&gt;Also some session logs of one of these messages passing through would be good&amp;nbsp;[:)]&lt;/p&gt;&lt;p&gt;FWIW a from address should never look like that. &lt;/p&gt;

[quote user="dilberts_left_nut"]

FWIW a from address should never look like that. 

[/quote]

Just for my own interest, can you clarify whether, if an incoming message was declared as having an envelope-from-address that WAS valid, but the message-from-address was in the above invalid format (or any other for that matter), would any error result?

[quote user=&quot;dilberts_left_nut&quot;]&lt;P&gt;FWIW a from address should never look like that.&nbsp; &lt;/P&gt;&lt;P&gt;[/quote]&lt;/P&gt;&lt;P&gt;Just for my own interest, can you clarify whether, if an incoming message was declared as having an envelope-from-address that WAS valid, but the message-from-address was in the above invalid format (or any other for that matter), would any error result?&lt;/P&gt;

I would expect the SMTP server to reject it, although if it was enclosed in <...> that may satisfy it.

 

I have a line in transflt.mer to reject on a whole series of characters that should not be there. This was originally to combat the inclusion of a | (pipe), presumably as an exploit for mail servers parsing addresses with shell scripts.

 

Come to think of it I also have lines to reject other 'bad' MAIL FROM's, like 'no @', 'no domain part' etc.

It may even have been as a response to the very problem of the OP! (it was a while ago now and I have been asleep since [:)])

 

Edit: Sorry, misread your post. AFAIK MercS & Core will only use the SMTP MAIL FROM (that's what gets logged anyway) and not even look at the From address in the message body.

&lt;p&gt;I would expect the SMTP server to reject it, although if it was enclosed in &amp;lt;...&amp;gt; that may satisfy it.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;I have a line in transflt.mer to reject on a whole series of characters that should not be there. This was originally to combat the inclusion of a | (pipe), presumably as an exploit for mail servers parsing addresses with shell scripts.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Come to think of it I also have lines to reject other &#039;bad&#039; MAIL FROM&#039;s, like &#039;no @&#039;, &#039;no domain part&#039; etc.&lt;/p&gt;&lt;p&gt;It may even have been as a response to the very problem of the OP! (it was a while ago now and I have been asleep since [:)]) &lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Edit: Sorry, misread your post. AFAIK MercS &amp;amp; Core will only use the SMTP MAIL FROM (that&#039;s what gets logged anyway) and not even look at the From address in the message body. &lt;/p&gt;
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Cancel
Delete
Pending draft ... Click to resume editing
Discard draft