Postfix hooking Dovecot quota (correct syntax)

2019-03-23 Thread Davide Marchi
Hi Friends, on Debian Stretch, Postfix 3.1.9 and Dovecot 2.2.27 I'm enabling user quota. Following this tutorial (suggested from Dovecot mailing list): https://blog.sys4.de/postfix-dovecot-mailbox-quota-en.html it is suggested to add in "main.cf" smtpd_recipient_restrictions = ...

Re: Postfix Active: active (exited) - (code=exited, status=0/SUCCESS)

2019-03-22 Thread Davide Marchi
. Reino ha scritto: On Fri, 22 Mar 2019, Davide Marchi wrote: [..] ● postfix.service - Postfix Mail Transport Agent Loaded: loaded (/lib/systemd/system/postfix.service; enabled; vendor preset: enabled) Active: active (exited) since Thu 2019-03-21 22:04:46 CET; 18h ago Process: 4453

Postfix Active: active (exited) - (code=exited, status=0/SUCCESS)

2019-03-22 Thread Davide Marchi
Hi Friends, on a VPS Debian Stretch, Postfix 3.1.9-0, Dovecot 2.2.27-3, rspamd 1.8.3-1, Clamav 0.100.2, postfix-mysql 3.1.9-0, dovecot-mysql 2.2.27-3 running "systemctl -l status postfix" obtain: ● postfix.service - Postfix Mail Transport Agent Loaded: loaded

Gnu Mailman, Postfix relay_domains and MySQL virtual domains/users tables

2019-02-28 Thread Davide Marchi
Hi Friends! I've just installed Mailman 2.1.23 on Debian Stretch, Postfix 3.1.8-0+deb9u1 + Dovecot 2.2.27 (c0f36b0) with "virtual_domains" "virtual_users" "virtual_aliases" on MySQL, and all seems works fine, but not tested on production environment again. I write you for clarification

Re: OpenDKIM SOCK path on Debian Jessie

2017-10-17 Thread Davide Marchi
Il 2017-10-16 19:07 A. Schulze ha scritto: [..] postfix and sendmail/milter use different notation to describe the same socket location. http://www.postfix.org/MILTER_README.html#smtp-only-milters vs. http://opendkim.org/opendkim.conf.5.html (search for "Socket" ...) to me your setup looks

OpenDKIM SOCK path on Debian Jessie

2017-10-16 Thread Davide Marchi
Hi Friends, I've set on (Debian Jessie, Posfix 2.11.3-1, Opendkim 2.9.2-2) /etc/default/opendkim: SOCKET="local:/var/spool/postfix/var/run/opendkim/opendkim.sock" and on /etc/postfix/main.cf: smtpd_milters = unix:/var/run/opendkim/opendkim.sock non_smtpd_milters =

Re: OpenDKIM on backup MX

2017-10-10 Thread Davide Marchi
Il 2017-10-10 16:36 Anvar Kuchkartaev ha scritto: You can use 2 separate keys on servers with different selectors and use 2 DNS records as public keys (for security reasons it will be better). Recipient of email will query dns record to identify if signature of the email is right or not.‎ It

OpenDKIM on backup MX

2017-10-10 Thread Davide Marchi
Hello friends, On Debian Jessie I would like to enable OpenDKIM on my two Postfix servers. My question is how to behave with the secondary backup server. Enable it as on the first and then I copy the key from first to secondary? And how I will write DNS txt record that must take the two

Re: ACL permission to move into different folder

2017-10-03 Thread Davide Marchi
Il 2017-10-03 17:06 Noel Jones ha scritto: [..] This is the postfix users list. You'll probably get more help on the dovecot users list. -- Noel Jones Hoops, sorry to all! thanks

ACL permission to move into different folder

2017-10-03 Thread Davide Marchi
Hi friends, I've set ACL for two user (two primary email address, no alias), where these users must not be able to delete email from imap server. Now I would like to add (from the client) the ability to move any incoming mail into different directory, if possible into an existing directory

Re: Increasing spam level to backup MX

2017-09-13 Thread Davide Marchi
Il 2017-09-11 14:23 Philip Paeps ha scritto: On 2017-09-11 14:13:29 (+0200), Davide Marchi wrote: activating a backup server I realized that some spammers using this server to send spam to my relay_recipient_maps addresses. Spam is then successfully forwarded to the main server

Increasing spam level to backup MX

2017-09-11 Thread Davide Marchi
Hi Friends, activating a backup server I realized that some spammers using this server to send spam to my relay_recipient_maps addresses. Spam is then successfully forwarded to the main server. Is there a parameter to prevent this type of action? A type check "do not receive email if the

Re: MX backup doesn't queue

2017-09-05 Thread Davide Marchi
Il 2017-09-01 22:57 Noel Jones ha scritto: [..] On the backup MX: [..] Well, finally we did it! Basically I think we can say that the backup server does not have to recognize as local, domains and addresses. This is what I did: "server1.org" the.backed-up.domain.tld (primary domain)

Re: MX backup doesn't queue

2017-09-03 Thread Davide Marchi
Il 2017-09-01 22:57 Noel Jones ha scritto: [..] On the backup MX: DO NOT list the domain in mydestination, virtual_alias_domains, or mailbox_domains parameters. These list domains for local delivery. You mean: do not list the domain of the *primary server* in mydestination,

MX backup doesn't queue

2017-09-01 Thread Davide Marchi
Hi friends, on a Debian Jessie and Postfix 2.11.x, where DNS configuration seem fine, infact if I shutdonwn the primary email server, the correspondence is delivered to the second correctly. where SERVER1 is "the.backed-up.domain.tld" where SERVER2 is "the backup MX) My point is to

Re: Postfix MX backup doesn't send to primary server

2017-08-27 Thread Davide Marchi
Il 2017-08-27 14:49 wie...@porcupine.org ha scritto: Davide Marchi: If I shut down the primary server, the MX backup receive the mail correctly and mail goes into mailbox 'INBOX'. Well that is the mistake. This server should not deliver to mailbox. Good, this is interesting, but a little

Postfix MX backup doesn't send to primary server

2017-08-27 Thread Davide Marchi
Hi friends, I'm wondering about an Postfix MX backup server correct configuration. I'm working on Debian Jessie and Postfix 2.11.x. If I shut down the primary server, the MX backup receive the mail correctly and mail goes into mailbox 'INBOX'. The problem is that if I try to look into the

Reject code for overquota and non-existent virtual users

2017-01-24 Thread davide marchi
Hi, my problem is that postfix respond with the same reject code for over-quota user and non-existent user (reject code 5.5.0 in both cases) ; is right for non-existent user but for over-quota is 5.5.2. my psotconf -n address_verify_map = alias_database = hash:/etc/aliases alias_maps =

Re: Postfix submission port closed

2016-10-21 Thread Davide Marchi
/dev/rob0 ha scritto: If you do encounter Postfix problems later, please see this link, which was given in the list welcome message, before posting again: http://www.postfix.org/DEBUG_README.html#mail Many thanks. Good bye -- cosmogoniA cosmogoniA n o p r o v a

Postfix submission port closed

2016-10-20 Thread Davide Marchi
Hi friends, I'm installing Postfix + Dovecot on my first VPS Debian Jessie, so I'mabeginner :-) using Christoph's workaround tutorial: https://workaround.org/ispmail/jessie. I've made some test, andthe previous oneshave gone well: 1) echo test | mail j...@example.org 2) mutt -f

Re: Differentiate sending from LMTP and SMTP based on email address

2016-04-28 Thread davide marchi
the correspondent email. In the above example my "MAIL FROM" is from this address davide.mar...@gmail.com. 2016-04-28 22:10 GMT+02:00 Wietse Venema <wie...@porcupine.org>: > davide marchi: > > Thanks to all, i put in > > /etc/postfix/main.cf > > transport_maps=hash/

Re: Differentiate sending from LMTP and SMTP based on email address

2016-04-28 Thread davide marchi
Venema <wie...@porcupine.org>: > davide marchi: > > Hi, my situation is this: > > Smarthost with postfix forwarding with lmtp to dovecot residing on > another > > host for whole domain > > Now i want to forward some emails of the same domain to same host but > > instead o

Differentiate sending from LMTP and SMTP based on email address

2016-04-28 Thread davide marchi
Hi, my situation is this: Smarthost with postfix forwarding with lmtp to dovecot residing on another host for whole domain Now i want to forward some emails of the same domain to same host but instead of lmtp i want to use smtp My question is how can i achieve this goal? Thanks in advance.