similar to: Bug: lmtp proxy does not quote local parts with spaces

On 26/10/2017 18:38, Alexander Dalloz wrote: > Am 26.10.2017 um 12:20 schrieb David Zambonini: >> >> There seems to be a bug with RFC822 processing in ltmp proxying that >> doesn't >> quote local parts that, for example, contain spaces. > > Newer related RFCs are RFC 5321 and 5322. Typo, meant to say RFC2822, which they still supercede, not that the

Hi again, I've not heard anything further regarding this bug, so I've had a look at the code. To restate the bug in a more precise way: LMTP in dovecot treats external RFC822 email addresses in the envelope recipient and internal usernames as almost identical/interchangeable. This is incorrect and leads to issues when attempting to use director as an LMTP proxy to proxy to recipients

On 26/10/2017 19:33, David Zambonini wrote: > On 26/10/2017 18:38, Alexander Dalloz wrote: >> Am 26.10.2017 um 12:20 schrieb David Zambonini: >>> >>> There seems to be a bug with RFC822 processing in ltmp proxying that >>> doesn't >>> quote local parts that, for example, contain spaces. >> >> Newer related RFCs are RFC 5321 and 5322.

Hi, Sorry, we're in a bit of a v2.3 merge frenzy. Much of the LMTP code will be replaced in v2.3, but I'll give the? older code a look as well. This can take a while though. Regards, Stephan. Op 1-11-2017 om 18:34 schreef David Zambonini: > Hi again, > > I've not heard anything further regarding this bug, so I've had a look at the code. > > To restate the bug

Am 26.10.2017 um 12:20 schrieb David Zambonini: > > There seems to be a bug with RFC822 processing in ltmp proxying that doesn't > quote local parts that, for example, contain spaces. Newer related RFCs are RFC 5321 and 5322. [ ... ] > MAIL FROM:<test at testdomain.com>\r\n > RCPT TO:<deemzed.uk+Junk E-mail>\r\n > > 501 5.5.4 Invalid.parameters\r\n That

On 07/11/2017 14:18, Mathieu R. wrote: > Maybe i got no answer because there is an error which seem obvious in my > logs : > > Nov 4 20:57:55 vps81550 dovecot: auth: Fatal: sql: driver not set in > configuration file /etc/dovecot/dovecot-sql.conf.ext This might sound silly, but in your doveconf you have: passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } Yet

I have a situation where my LMTP RCPT TO: goes to a mailbox user account that does not reflect either the final (through aliasing) or envelope email address. SMTP RCPT TO: (envelope-local-part at envelope-domain) Final Recipient: (final-local-part at final-domain) LMTP RCPT TO: (mailbox-local-part at mailbox-domain) I'd like to use the final recipient as the vacation address, but also

On 03/11/2017 11:48, Stephan Bosch wrote: > Hi, > > Sorry, we're in a bit of a v2.3 merge frenzy. Much of the LMTP code will be > replaced in v2.3, but I'll give the? older code a look as well. > > This can take a while though. Thank you very much for getting back to me, I can appreciate it can get hectic, and I don't wish to appear ungrateful, I wholeheartedly

I have a windows 2003 AD domain and a server joined to that domain. Winbind is being used as an idmap. Most everything seems to work fine. Winbind gets user info correctly: [root@samba ~]# wbinfo -u TESTDOMAIN\administrator TESTDOMAIN\guest TESTDOMAIN\support_388945a0 TESTDOMAIN\krbtgt TESTDOMAIN\swhaley TESTDOMAIN\test [root@samba ~]# wbinfo -g BUILTIN\administrators BUILTIN\users

> Hi all, > > We have a Samba AD DC service running on Ubuntu 16.0.4 with Samba > 4.3.11. We are planning to upgrade it to a recent version, probably > 4.8.3. > > I think that I have two options: > > a) Package upgrade via 3rd party repositories (Louis Van Belle's repo) > by following wiki. > > b) A fresh install of 4.8.3 on another VM then join it to

Hi , I have set up a 2-node CTDB cluster serving NFS and CIFS authenticating Windows and Linux users via Active Directory. The setup works fine, except only one server in the CTDB-cluster is able to join the AD domain at a given instance. If you manually add the other server into AD, the already connected server gets disconnected. There is no specific error message logged in /var/log/message or

auth_username_translation seems to be appliet on RCPT TO address of LTMP transport. Why dovecot is doing that? And better question - is there a way to disable auth_username_translation for LTMP but leave enabled for the rest (imap, pop3 etc) ? Background: I'm doing auth_username_translation = @= to allow logins like aaa at bbb.pl to be internally translated to aaa=bbb.pl. That works

Has re-opening the logfiles broken between 2.2.32 and 2.2.33 releases? Using the same config that I've had for the past 10 or so point releases, /usr/bin/doveadm log reopen works perfectly up until 2.2.32, but with 2.2.33 (and .1 and .2) no new logfiles are created, file descriptors still have the original files open and keep writings to those logs. On an idling test instance, I get: master:

On 07.11.2017 08:54, Aki Tuomi wrote: > > On 06.11.2017 23:31, David Zambonini wrote: >> Has re-opening the logfiles broken between 2.2.32 and 2.2.33 releases? >> >> Using the same config that I've had for the past 10 or so point >> releases, /usr/bin/doveadm log reopen works perfectly up until 2.2.32, >> but with 2.2.33 (and .1 and .2) no new logfiles are

Hi, I'm using dovecot with a passdb-file . When I login using : test at testdomain.com I notice dovecot strips off the domainname and looks up everything in front of the @ in his passdb-file... So I went on to configure the following in my dovecot.conf : auth_username_format = %u@%d restarted dovecot, but he still strips of the @ and the domainname ... LOG (sorry for f* up format) :

Red Hat Enterprise Linux Server release 5.2 (Tikanga) - x86_64 Samba - 3.0.28-0.el5.8 Objective: To have samba authenticate against AD and utilize the values set for the AD rfc2307 schema. Problem: Values stored in AD are not being used. The samba server has successfully joined the AD, but when I do a getent passwd | grep <user> the uid, none of the values returned match what is stored in

Not to stir the pot, but I notice my email address has recently been harvested from this list for spamming purposes. This email address is unique and not used for anything else. I'd distinguish this from spam sent to the mailing list itself, which is obviously different. Is there anything further that could be done to prevent this? -- Dave

On 4/14/15, J. Echter <j.echter at echter-kuechen-elektro.de> wrote: > Am 14.04.2015 um 14:04 schrieb J. Echter: >> Hi, >> >> we're using thunderbird as our client, it has the functionality to >> sort spamassassin tagged mails in a folder called 'Junk'. >> >> I have this folder on my dovecot server and i'd like to use the >>

Hi, we're using thunderbird as our client, it has the functionality to sort spamassassin tagged mails in a folder called 'Junk'. I have this folder on my dovecot server and i'd like to use the recipient_delimiter feature to get my spam/junk mails directly to this folder. what i have done yet: dovecot.conf: plugin { recipient_delimiter = + } postfix: master.cf dovecot

I am running Samba ver 3.0.33 on Solaris 10 (sparc) as a PDC with LDAP for the backend for both samba and unix accounts. I have also set up a trust with an Windows domain- lets call it WINDOMAIN- (the PDC for the Windows domain is Win 2003 but is in mixed mode for backwards compat.) The SAMBA domain trusts the WINDOWS domain, not not vice versa. I had also tried setting up trusts with