search for: sprovide

..., SUBSCRIBE, NOTIFY..Contact: <sip:4212326 60145@195.195.12.223>..Content-Length: 0.... U 195.195.12.223:5060 -> 200.100.100.123:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 200.100.100.123:5060;branch=z9hG4bK1362d770;received=200.100.100.123;rport=5060..From: <sip:4221917293125@sip1.gt sprovider.sk>;tag=as51ddb092..To: <sip:4221917293125@sip1.provider.com>;tag=as17802cd7..Call-ID: 0c74fd93144a92174f3a032d4aeca8dc@200.100.100.123 ..CSeq: 103 REGISTER..User-Agent: SoftSwitch v1.0..Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY..Expires: 1 200..Contact: <s...

...he line saying > > From: abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz at example.com > > becomes > > rstuvwxyzabcdefghijklmnopqrstuvwxyz at example.com > > > So: Could we please stop blaming fetchmail for this? > It's just the messenger. Could you also sprovide your "dovecot -n" output and any warnings and errors in dovecot logs. br, Teemu Huovila

...bcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz at example.com >> >> becomes >> >> rstuvwxyzabcdefghijklmnopqrstuvwxyz at example.com >> >> >> So: Could we please stop blaming fetchmail for this? >> It's just the messenger. > Could you also sprovide your "dovecot -n" output and any warnings and errors in dovecot logs. Ah, found the dovecot -n earlier in the thread, but the logs would still be relevant. Teemu

Am 04.05.2015 um 21:04 schrieb Santiago Vila: > Greetings. > > Thanks to Jelmer Vernooij, who has just uploaded version 2.2.16 for > Debian unstable, I can confirm that this bug may still be reproduced > in version 2.2.16, so it has *not* been fixed yet. > > Several months ago I was told "I can't reproduce it in dovecot hg", or > something like that. Well,