- dovecot - dovecot.org

[Dovecot] Idea: POP3 deletion as a flag
by Timo Sirainen 14 May '13

14 May '13

GMail doesn't delete mails when POP3 client issues a DELE command for it. Instead they just become invisible for future POP3 sessions, but they still exist for IMAP/webmail. The same could be implemented pretty easily for Dovecot: - Add a new setting to enable this: pop3_deleted_flag = $POP3Deleted - When DELEting a message, add this flag to the message. - When listing messages, skip all messages that have this flag. - Also hide this flag from IMAP clients(?) Thoughts? Probably 20 lines of new code.

18 44

[Dovecot] ot: mirroring/archiving to a Mac?
by voytek＠sbt.net.au 14 May '13

14 May '13

I have Doveot 2.1.1 on Centos, all's well user mails are kept for 60 days, then, 'aged off' (deleted) a Mac user with two domains and two dozen users asked me: can I set a mail server on my home Mac server, and, 'mirror' the real mail server mailboxes so than I can have an offline mail archive for ever ? I know very little about Macs, can I setup dovceot on Mac? any tips/suggestions/howtos for mirroring/archiving as so?

5 6

[Dovecot] Pigeonhole: Typo in 20-managesieve.conf
by Gedalya 12 May '13

12 May '13

Line 33: #process_count = 1024 Probably you mean process_limit

2 1

[Dovecot] Any way to let dovecot block pop3 attempts?
by Steve Campbell 12 May '13

12 May '13

Is there a way using dovecot facilities to block an IP from attempting POP3 connections (similar to the sendmail access file for smtp connections)? I usually do this at my border firewall, but if there's a quick and dirty way in dovecot to do this, it'd make life a little simpler. Thanks steve campbell

7 10

[Dovecot] Problem with LDA reject message
by Davide 11 May '13

11 May '13

Hi to all, i have a problem with LDA when users are quota-full. My setup is Vpopmail + dovecot + lda; if i send a messagge internally to a user with quota full i receive correctly a messagge but in the header ( i attacch a snip) From - Fri May 10 14:42:27 2013 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 X-Mozilla-Keys: Return-Path: <"<>"@mail.cgilfe.it> i receive this strange Return-Path. I the messagge is sent outside other servers reply with this messagge: Subject: failure notice Hi. This is the qmail-send program at mail.cgilfe.it. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. <Roberta.Luzzi(a)filcams.cgil.it>: Connected to 80.207.169.234 but sender was rejected. Remote host said: 501 Address Syntax Error in <"<>"@mail.cgilfe.it> this is my .qmail-default file: |/var/qmail/bin/preline -f /usr/local/libexec/dovecot/dovecot-lda -d $EXT@$USER | /home/vpopmail/bin/vdelivermail "" bounce-no-mailbox Thanks in advance. -- *Davide Marchi* *T*eorema *F*errara *Srl* Via Spronello, 7 - Ferrara - 44121 Tel. *0532783161* Fax. *0532783368* E-m@il: *davide.marchi(a)mail.cgilfe.it* Skype: *davide.marchi73* Web: *http://www.cgilfe.it* *CONFIDENZIALITA'* *Ai sensi del D.Lgs. 196/2003 si precisa che le informazioni contenute in questo messaggio sono riservate ed a uso esclusivo del destinatario/dei destinatari. Qualora il messaggio in parola Le fosse pervenuto per errore, La invitiamo ad eliminarlo senza copiarlo e a non inoltrarlo a terzi, dandocene gentilmente comunicazione.* *Per favore, pensa all'ambiente. Stampa questa email solo se necessario.*

2 1

Re: [Dovecot] Any way to let dovecot block pop3 attempts?
by Joseph Tam 11 May '13

11 May '13

Steve Campbell writes: > I use Centos and the default dovecot RPM. I seem to recall there was a > way to determine if dovecot was built with "--with-libwrap". Can anyone > shed light on how to determine this, please? Maybe dovecot --build-options Or you can just test it directly by denying a connection to a test host. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] Remove Return-Path in lda rejection message
by Davide 11 May '13

11 May '13

Is it possible to remove return-path in dovecot lda rejection? -- *Davide Marchi* *T*eorema *F*errara *Srl* Via Spronello, 7 - Ferrara - 44121 Tel. *0532783161* Fax. *0532783368* E-m@il: *davide.marchi(a)mail.cgilfe.it* Skype: *davide.marchi73* Web: *http://www.cgilfe.it* *CONFIDENZIALITA'* *Ai sensi del D.Lgs. 196/2003 si precisa che le informazioni contenute in questo messaggio sono riservate ed a uso esclusivo del destinatario/dei destinatari. Qualora il messaggio in parola Le fosse pervenuto per errore, La invitiamo ad eliminarlo senza copiarlo e a non inoltrarlo a terzi, dandocene gentilmente comunicazione.* *Per favore, pensa all'ambiente. Stampa questa email solo se necessario.*

2 1

[Dovecot] Expunge mailbox from script
by Paul van der Vlis 10 May '13

10 May '13

Hello, I would like to expunge all mail of a mailbox from a script. What's a good tool to do that? With regards, Paul van der Vlis. -- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl/

2 1

Re: [Dovecot] change inbox dotlock name
by Chris Saldanha 10 May '13

10 May '13

Axel Luttgens <AxelLuttgens(a)swing.be> wrote: > But I fear I don't understand your problem description. > Could you elaborate? Hi Axel, The issue is that the procmail port on FreeBSD doesn't acquire a dotlock when it's the default lock file (/var/mail/username.lock). It prints that it's bypassing the dotlock and just does a lockf() lock after. Looking in the code for procmail, it seems that it's being too clever with a bunch of checks and so it doesn't try to get the lock -- it's decided it doesn't want to before doing it. The permissions and runtime environment permit the lock, and the same lock is acquired correctly by dovecot when writing to the inbox. I'm doing dotlock and then lockf() locking in all the mail software. procmail's checks only seem to apply to the default lock file for the inbox. If I specify an alternate name in the .procmailrc for the $ORGMAIL delivery of the message, then it will acquire any other lock I ask, including an alternate name in the /var/mail directory. I'll dig into the procmail sources as needed to resolve it, but I had hoped that I could get dovecot to lock with a different filename, because that would resolve the issue with minimal hackery... Cheers, Chris -- Chris Saldanha Parliant Corporation

2 1

[Dovecot] dovecot not logging after upgrade to 2.1.7 on debian
by Steinar Bang 09 May '13

09 May '13

After upgrading my IMAP server to the new debian stable, and upgrading dovecot from 1.x to 2.1.7 in the process, dovecot no longer logs anything to /var/log/mail.*. The last entries there are from before the upgrade, and no starts or error messages or failed login attempts, since then, have been logged. Does anyone know what might cause this? "doveconf -n" doesn't mention any of the log settings. Maybe the log settings aren't picked up? What could be done to make sure they are picked up? Here's the content of the /etc/dovecot/conf.d/10-logging.conf file: ## ## Log destination. ## # Log file to use for error messages. "syslog" logs to syslog, # /dev/stderr logs to stderr. log_path = syslog # Log file to use for informational messages. Defaults to log_path. #info_log_path = # Log file to use for debug messages. Defaults to info_log_path. #debug_log_path = # Syslog facility to use if you're logging to syslog. Usually if you don't # want to use "mail", you'll use local0..local7. Also other standard # facilities are supported. syslog_facility = mail ## ## Logging verbosity and debugging. ## # Log unsuccessful authentication attempts and the reasons why they failed. #auth_verbose = no # In case of password mismatches, log the attempted password. Valid values are # no, plain and sha1. sha1 can be useful for detecting brute force password # attempts vs. user simply trying the same password over and over again. #auth_verbose_passwords = no # Even more verbose logging for debugging purposes. Shows for example SQL # queries. #auth_debug = no # In case of password mismatches, log the passwords and used scheme so the # problem can be debugged. Enabling this also enables auth_debug. #auth_debug_passwords = no # Enable mail process debugging. This can help you figure out why Dovecot # isn't finding your mails. #mail_debug = no # Show protocol level SSL errors. #verbose_ssl = no # mail_log plugin provides more event logging for mail processes. plugin { # Events to log. Also available: flag_change append #mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename # Available fields: uid, box, msgid, from, subject, size, vsize, flags # size and vsize are available only for expunge and copy events. #mail_log_fields = uid box msgid size } ## ## Log formatting. ## # Prefix for each line written to log file. % codes are in strftime(3) # format. #log_timestamp = "%b %d %H:%M:%S " # Space-separated list of elements we want to log. The elements which have # a non-empty variable value are joined together to form a comma-separated # string. #login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c # Login log format. %$ contains login_log_format_elements string, %s contains # the data we want to log. #login_log_format = %$: %s # Log prefix for mail processes. See doc/wiki/Variables.txt for list of # possible variables you can use. #mail_log_prefix = "%s(%u): " # Format to use for logging mail deliveries. You can use variables: # %$ - Delivery status message (e.g. "saved to INBOX") # %m - Message-ID # %s - Subject # %f - From address # %p - Physical size # %w - Virtual size #deliver_log_format = msgid=%m: %$

4 6