On 2015-01-06 02:02, gilles chehade wrote:
> A new opensmtpd portable snapshot is available at:
> 
>         http://www.opensmtpd.org/archives/opensmtpd-201501060207p1.tar.gz
> 
> Checksum:
> 
>   SHA256 (opensmtpd-201501060207p1.tar.gz) =
>   a99c3bd695c494ac5253ffbafc1351203d44cf1a51d05b59d1b8379a94682bea
> 
> A summary of the content of this snapshot is available below.
> 
> Please test and let us know if it breaks something!
> 
> If this snapshot doesn't work, please also test with a previous one,
> to help us spot where the issue is coming from. You can access all
> previous snapshots here:
> 
>         http://www.opensmtpd.org/archives/
> 
> The OpenSMTPD team ;-)
> 
> 
> Summary of changes since last snapshot (opensmtpd-201412241507p1):
> -----------------------------------------------------------------
> 
>     - make Received: header conform a little bit more with RFC2821 and fix 
> sorting in mutt [1]

Huh, I never did manage to get mutt's sorting (by recv date) fixed, and I never
would have guessed it was a header issue.
Is there some way to update/fix already received email? Exactly what changes in
the emails?

>     - add forward-only documentation [2]
>     - use explicit_bzero() where appropriate
>     - remove dead commented code
>     - properly save errno
>     - prepend From line separator when using delivery_{mda,filename}
>     - make SNI code more straightforward
>     - skip comments when searching insert point for domain append, fixes 
> broken From header
>     - add support for tags matching in "sender" and "recipient" smtpd.conf 
> keywords
> 
> [1] Author: Armin Wolfermann <[email protected]>
> [2] Author: Jason Barbier <[email protected]>
> 
> -- 
> You received this mail because you are subscribed to [email protected]
> To unsubscribe, send a mail to: [email protected]
> 

-- 
Hugo Osvaldo Barrera
A: Because we read from top to bottom, left to right.
Q: Why should I start my reply below the quoted text?

Attachment: pgpF7DFVyzYGj.pgp
Description: PGP signature

Reply via email to