Re: [exim] Reading confirmation email

Inizio della pagina
Delete this message
Reply to this message
Autore: Jeremy Harris
Data:  
To: exim-users
Oggetto: Re: [exim] Reading confirmation email
On 01/11/2013 04:36 PM, tovis wrote:
> I'm using exim4 configured with "smart host" on Debian Squeeze.
> Also I have fetchmail, courier IMAP and apache2, php5, squirrelmail combo
> for mailing (I have several two booting boxes with win and linux - it was
> the easiest way to have mailing infrastructure for both systems). For long
> time I have no pőropblems, but now I have got several error messages from
> my "smart host":
> Header (as it shown in Squirrelmail):
> Return-path: <>
> Envelope-to: postmaster@???
> Delivery-date: Wed, 09 Jan 2013 10:30:40 +0100
> Received: from Debian-exim by samu.bubu.dyndns.ws with local (Exim 4.63)
>       id 1Tsrzc-0001Lv-DR
>       for postmaster@???; Wed, 09 Jan 2013 10:30:40 +0100
> Auto-Submitted: auto-replied
> From: Mail Delivery System <Mailer-Daemon@???>
> To: postmaster@???
> Subject: Message frozen
> Message-Id: <E1Tsrzc-0001Lv-DR@???>
> Date: Wed, 09 Jan 2013 10:30:40 +0100

>
> Message (as it shown in Squirrelmail):
> Message 1Tsrzb-0001Ls-U7 has been frozen (delivery error message).
> The sender is <>.
>
> The following address(es) have yet to be delivered:
>    some.one@???: SMTP error from remote mail server after MAIL FROM:<>
> SIZE=2673: host smtp.upcmail.hu [213.46.255.2]: 550 5.1.0 <> sender rejected

>
> I think these emails are reading confirmation.
> I think, that problem is "Return path" and "sender" fields are empty.
> It could be solved by exim4 configuration? It could be the problem of
> exim4? I'm not sure :(
> Any help?


Is smtp.upcmail.hu you, or under your control? Is it your smart-host?
It looks like it's trying to deliver an empty-sender mail to "bigfirm.hu".

What's the relationship with your "dyndns.ws" address; why did it send this
notification there?

Can you find out why the empty-sender mail was produced? They're legitimate for
Delivery Status Notifications (DSNs), of which one class is a "bounce" (that is, a notification
of failure to deliver).
Have a look at your logs.

It could just be that "bigfirm" are clueless, in rejecting all DSNs.

It could, at the same time, be that some spammer faked a "bigfirm" sender
address, and you accepted the spam and only later decided you couldn't
deliver it, so you generated a bounce. This is legal per the mail protocol
standards, but suboptimal in a spam-filled world. If so you need to work
harder at spotting and rejecting spam during the SMTP conversation.

-- 
Cheers,
    Jeremy