libsrs_alt library (used by exim to generate SRS addresses for example; copy on https://github.com/LynxChaus/libsrs-alt) has an option:
" --with-base64compat This option alters the behaviour of the base64 encoder built in to libsrs_alt to use the non-standard characters '_' and '.' instead of '+' and '/'. This move vastly improves the compatibility of SRS with MTAs. The option comes highly recommended. " which producess addresses like this: $ srs --alias=example.com --secret=1386 --forward t...@test.pl SRS0=GW..5e=YD=test.pl=t...@example.com (note two dots instead of two slashes; without base64compat option that would be SRS0=GW//5e=YD=test.pl=t...@example.com) but google refuses these claiming that it violates RFC-5321 (which IMO isn't true as this is valid RFC5321 address) $ telnet aspmx.l.google.com 25 Trying 2a00:1450:400c:c0c::1a.25... Connected to wr-in-x1a.1e100.net. Escape character is '^]'. 220 mx.google.com ESMTP ue16si22842569wjb.138 - gsmtp ehlo test 250-mx.google.com at your service, [2001:67c:267c:1:3::2] 250-SIZE 157286400 250-8BITMIME 250-STARTTLS 250-ENHANCEDSTATUSCODES 250-PIPELINING 250-CHUNKING 250 SMTPUTF8 mail from: <SRS0=GW..5e=YD=test.pl=t...@example.com> 553-5.1.2 The sender address <SRS0=GW..5e=YD=test.pl=t...@example.com> is not a 553 5.1.2 valid RFC-5321 address. ue16si22842569wjb.138 - gsmtp Can anyone from google take a look at adding dots handling in srs hash? Thanks, -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) _______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
