search for: deemz

...result_internalfail = return-fail } } lmtp.ext: password_query = SELECT 'y' AS proxy, NULL AS password, 'y' AS nopassword FROM users WHERE userName='%Ln' from exim -> director LMTP network dump: MAIL FROM:<test at testdomain.com>\r\n RCPT TO:<"deemzed.uk+Junk E-mail"@mailbox.localhost>\r\n DATA\r\n (etc) .\r\n 501 5.5.4 Invalid parameters\r\n QUIT\r\n from director -> dovecot LMTP network dump: 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 I'll try...

...al 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 local-part spec has changed. :) > > [ ... ] > >> 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 recipient address is totally invalid. It is neither just a local > part without a domain, nor a plussed address destination. > > Check your setup with i.e. > > RCPT TO:<"Junk E-mail&...

...gt;> >> Newer related RFCs are RFC 5321 and 5322. > > Typo, meant to say RFC2822, which they still supercede, not that the > local-part spec has changed. :) > >> >> [ ... ] >> >>> 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 recipient address is totally invalid. It is neither just a local >> part without a domain, nor a plussed address destination. >> >> Check your setup with i.e. >> >&g...

...RFC 5321 and 5322. >>> Typo, meant to say RFC2822, which they still supercede, not that the >>> local-part spec has changed. :) >>> >>>> [ ... ] >>>> >>>>> 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 recipient address is totally invalid. It is neither just a local >>>> part without a domain, nor a plussed address destination. >>>> >>>> Che...

...2: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 recipient address is totally invalid. It is neither just a local part without a domain, nor a plussed address destination. Check your setup with i.e. RCPT TO:<"Junk E-mail"@deemzed.uk> or RCPT TO:<&qu...

...s are RFC 5321 and 5322. >> >> Typo, meant to say RFC2822, which they still supercede, not that the >> local-part spec has changed. :) >> >>> >>> [ ... ] >>> >>>> 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 recipient address is totally invalid. It is neither just a local >>> part without a domain, nor a plussed address destination. >>> >>> Check your set...

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 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

Quoting dovecot-e51 at deemzed.uk: > 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 > obviou...

On 02/12/2018 05:31, M. Balridge wrote: > Quoting dovecot-e51 at deemzed.uk: > >> 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 its...

On Sun, Dec 02, 2018 at 10:09:02AM +1000, Noel Butler wrote: > On 02/12/2018 05:31, M. Balridge wrote: > > > Quoting dovecot-e51 at deemzed.uk: > > > >> 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 spa...

On pop3 logout, we're seeing log lines where the deleted count is blank (using default pop3_logout_format), so "del=%d/%m" is displaying in the logs as: "del=/1186" for example. In src/pop3/pop3-client.c:552: tab[4].value = client->delete_success ? dec2str(client->deleted_count) : 0; Shouldn't this be: tab[4].value =

On 19/07/2017 11:23, mj wrote: > Hi Robert, > > On 07/18/2017 11:43 PM, Robert Schetterer wrote: >> i guess not, but typical bots arent using ssl, check it >> >> however fail2ban sometimes is to slow > > I have configured dovecot with > auth_failure_delay = 10 secs > > I hope that before the 10 sec are over, dovecot will have logged about the >

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:

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

Hi everyone, first post to the list, be gentle with me! Perhaps I'm missing something here, but it appears to me that many password database extra fields currently aren't much use inside SQL queries? All boolean fields like nologin/nodelay/nopassword are set if the column is present in the returned query, regardless of value (including NULL) For example, say you have a query like:

Hi, I'm attempting to proxy lmtp using director to hash to the same backend as pop3/imap. My pop3/imap users are of the form: username and my lmtp users are of the form: <username at domain> Where domain is fairly redundant but does carry some useful information. Now, I can proxy lmtp using user=%{username} and destuser=%{orig_user}, and this all appears to work correctly.

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

On 02/06/2016 22:58, Timo Sirainen wrote: > On 01 Jun 2016, at 16:48, Alessio Cecchi <alessio at skye.it> wrote: >> >> Hi, >> >> after the last upgrade to Dovecot 2.2.24.2 (d066a24) I see an increased number of errors "Broken MIME parts" for users in dovecot log file, here an example: >> >> Jun 01 15:25:29 Error: imap(alessio.cecchi at