Displaying 7 results from an estimated 7 matches for "b5a2".
Did you mean:
b52
2019 Jun 14
2
Dovecot LMTP rejecting mail from address with apostrophe
Hi,
I have an OpenSMTPD / Dovecot installation on an OpenBSD server. I recently came across an issue where Dovecot LMTP would reject a message sent to a local user from an address which contains a single apostrophe (e.g. firstname.o'lastname at example.com). Apparently apostrophe, as well as a number of other special characters, are valid characters in the local part of the email address
2017 Oct 24
2
brick is down but gluster volume status says it's fine
...138: option rpc-auth-allow-insecure on
> 139: option auth.addr./export/brick7/digitalcorpora.allow
> 129.174.125.204,129.174.93.204
> 140: option auth-path /export/brick7/digitalcorpora
> 141: option auth.login.b17f2513-7d9c-4174-a0c5-de4a752d46ca.password
> 6c007ad0-b5a2-4564-8464-300f8317e5c7
> 142: option auth.login./export/brick7/digitalcorpora.allow
> b17f2513-7d9c-4174-a0c5-de4a752d46ca
> 143: subvolumes digitalcorpora-io-stats
> 144: end-volume
> 145:
> 146: volume digitalcorpora-server
> 147: type protocol/server
> 148:...
2017 Oct 24
0
brick is down but gluster volume status says it's fine
...-auth-allow-insecure on
>> 139: option auth.addr./export/brick7/digitalcorpora.allow
>> 129.174.125.204,129.174.93.204
>> 140: option auth-path /export/brick7/digitalcorpora
>> 141: option auth.login.b17f2513-7d9c-4174-a0c5-de4a752d46ca.password
>> 6c007ad0-b5a2-4564-8464-300f8317e5c7
>> 142: option auth.login./export/brick7/digitalcorpora.allow
>> b17f2513-7d9c-4174-a0c5-de4a752d46ca
>> 143: subvolumes digitalcorpora-io-stats
>> 144: end-volume
>> 145:
>> 146: volume digitalcorpora-server
>> 147: type...
2019 Jun 14
0
Dovecot LMTP rejecting mail from address with apostrophe
...at example.com> to=<me at example.org> rcpt=<me at example.org> user=me delay=0s result=PermFail stat=Error ("mail.lmtp: LMTP server error: 501 5.5.4 Invalid FROM: Invalid character in localpart")
That's essentially the same bug as mentioned in
<6386018f-22b2-9562-b5a2-36e81cbe2892 at debian.org> (bounces on invalid
UTF-8 in localpart) that got assigned DOP-1045. Dovecot LDA and LMTP
should just not care about remote address validity when delivering
locally. It's not the LDA's business.
2019 Jun 14
2
Dovecot LMTP rejecting mail from address with apostrophe
...le.com> to=<me at example.org> rcpt=<me at example.org> user=me delay=0s result=PermFail stat=Error ("mail.lmtp: LMTP server error: 501 5.5.4 Invalid FROM: Invalid character in localpart")
>
> That's essentially the same bug as mentioned in <6386018f-22b2-9562-b5a2-36e81cbe2892 at debian.org> (bounces on invalid UTF-8 in localpart) that got assigned DOP-1045. Dovecot LDA and LMTP should just not care about remote address validity when delivering locally. It's not the LDA's business.
Ah, thanks a lot for that. I was trying to find any information a...
2019 Jun 24
1
Dovecot LDA error - Invalid -f parameter: Invalid character in path
Hi list.
I'm using dovecot as postfix's LDA. The version is 2.3.6.
Last week some spammer set the envelope's FROM to "foo at bar@domain.com"
(with two @). While trying to deliver (as this one didn't hit the
spamassassin's score), dovecot said the following:
Jun 21 02:35:58 mymailserver postfix/pipe[29736]: ADA268195E:
to=<user at mydomain>, relay=dovecot,
2017 Dec 21
1
seeding my georeplication
Thanks for your response (6 months ago!) but I have only just got around to
following up on this.
Unfortunately, I had already copied and shipped the data to the second
datacenter before copying the GFIDs so I already stumbled before the first
hurdle!
I have been using the scripts in the extras/geo-rep provided for an earlier
version upgrade. With a bit of tinkering, these have given me a file