On Tue, 13 Nov 2012 11:02:00 +0100, Alexander Hall wrote:
> Since I switched to SMTPD I noticed a few cron emails being marked as
> spam by spamassassin, largely caused by the From: and To: headers not
> containing a domain part.
Sendmail will add the domain if the always_add_domain feature is
en
On Tue, Nov 13, 2012 at 03:14:06PM +0100, Alexander Hall wrote:
> On 11/13/12 13:49, Christian Weisgerber wrote:
> >Alexander Hall wrote:
> >
> >>Since I switched to SMTPD I noticed a few cron emails being marked as
> >>spam by spamassassin, largely caused by the From: and To: headers not
> >>con
> Date: Tue, 13 Nov 2012 15:14:06 +0100
> From: Alexander Hall
>
> On 11/13/12 13:49, Christian Weisgerber wrote:
> > Alexander Hall wrote:
> >
> >> Since I switched to SMTPD I noticed a few cron emails being marked as
> >> spam by spamassassin, largely caused by the From: and To: headers not
>
On 11/13/12 13:49, Christian Weisgerber wrote:
Alexander Hall wrote:
Since I switched to SMTPD I noticed a few cron emails being marked as
spam by spamassassin, largely caused by the From: and To: headers not
containing a domain part.
If I read RFC822 correctly, the domain part is not optiona
Alexander Hall wrote:
> Since I switched to SMTPD I noticed a few cron emails being marked as
> spam by spamassassin, largely caused by the From: and To: headers not
> containing a domain part.
>
> If I read RFC822 correctly, the domain part is not optional, and thus
> we should append one, unle
Since I switched to SMTPD I noticed a few cron emails being marked as
spam by spamassassin, largely caused by the From: and To: headers not
containing a domain part.
If I read RFC822 correctly, the domain part is not optional, and thus
we should append one, unless MAILTO already specifies one.
Hi
