Re: catch-all not working with postfix dovecot lda

2010-04-17 Thread mouss
fakessh a écrit :
> On Thu, 15 Apr 2010 08:33:43 -0500, Noel Jones 
> wrote:
>> On 4/14/2010 3:42 PM, fakessh wrote:
>>> On Wed, 14 Apr 2010 13:50:34 -0500, Noel Jones
>>> wrote:
 On 4/14/2010 1:45 PM, fakessh wrote:
> On Wed, 14 Apr 2010 14:12:25 -0400, Charles Marcus
>wrote:
>>>
>>> I changed the entries @fakessh to r...@localhost in
> /etc/postfix/virtual
>>> postmap then a file  to
>>> the postfix restart.
>>>
>>> all without success, or rather the same mistake

> [snip]

> 
> my jed /etc/postfix/virtual
> #
> # AUTHOR(S)
> #Wietse Venema
> #IBM T.J. Watson Research
> #P.O. Box 704
> #Yorktown Heights, NY 10598, USA
> #
> #
> VIRTUAL(5$
> postmas...@fakessh.eu   r...@localhost.r13151.ovh.net
> fake...@fakessh.eu fake...@localhost.r13151.ovh.net
> webm...@fakessh.eu webm...@localhost.r13151.ovh.net
> se...@fakessh.eu   se...@localhost.r13151.ovh.net
> @fakessh   r...@localhost.r13151.ovh.net

fakessh != fakessh.eu.
you want:

@fakessh.eu r...@localhost.r13151.ovh.net


> [snip]


Re: postcat ENVELOPE RECORDS output?

2010-04-17 Thread mouss
Curtis a écrit :
>> It's not documented, because there is no promise that it will work
>> the same way in a future Postfix version.
>>
>> However, the names of the records give a hint.
>>
>>> Most particularly, I'm concerned about the following three fields:
>>>
>>> named_attribute: dsn_orig_rcpt=rfc822;em...@example.com
>>> original_recipient: em...@example.com
>>> recipient: em...@example.com
>>>
>>> Would it be safe to say that all local recipients of the message will be
>>> found in the "recipient:" field?  (Repeated for each recipient?)
>> That's how Postfix works at the moment, but there is no promise
>> that it will always work that way.
> 
> A quick follow up on this. The field I was actually looking for turned out
> to be "original_recipient:".  Just in case anybody else goes through this,
> let me document what I've learned about these three fields:
> 
>>> named_attribute: dsn_orig_rcpt=rfc822;em...@example.com 
> 
> Well, I'm not really sure where this value comes from,

as the name suggests, this is found in a DSN attribute. DSN (Delivery
Status Notification) is described in the corresponding RFCs.

> but it can not be
> used as a reliable way to determine who the local recipient is.  Sometimes
> it contains a non-local list address. 
> 
>>> original_recipient: em...@example.com
> 
> This one appears to be the actual local recipient that was probably captured
> during the smtp session.
> 
>>> recipient: em...@example.com
> 
> This value is what appears to be what postfix translated the address to
> after it accepted the message.  For example, if you use virtual_alias_maps
> to alias one address to another, then it will contain the target email
> address.
> 
> Again, as Wietse would say, these values are not guaranteed to work this way
> in future versions of Postfix.  In fact, they may not even work this way in
> the current version.  I'm using version 2.5.6.
> 
> Thanks,
> 
> Curtis
> 
> 



Re: catch-all not working with postfix dovecot lda

2010-04-17 Thread fakessh
On Sat, 17 Apr 2010 14:26:22 +0200, mouss  wrote:
> fakessh a écrit :
>> On Thu, 15 Apr 2010 08:33:43 -0500, Noel Jones 
>> wrote:
>>> On 4/14/2010 3:42 PM, fakessh wrote:
 On Wed, 14 Apr 2010 13:50:34 -0500, Noel
Jones
 wrote:
> On 4/14/2010 1:45 PM, fakessh wrote:
>> On Wed, 14 Apr 2010 14:12:25 -0400, Charles Marcus
>>wrote:

 I changed the entries @fakessh to r...@localhost in
>> /etc/postfix/virtual
 postmap then a file  to
 the postfix restart.

 all without success, or rather the same mistake
> 
>> [snip]
> 
>> 
>> my jed /etc/postfix/virtual
>> #
>> # AUTHOR(S)
>> #Wietse Venema
>> #IBM T.J. Watson Research
>> #P.O. Box 704
>> #Yorktown Heights, NY 10598, USA
>> #
>> #
>> VIRTUAL(5$
>> postmas...@fakessh.eu   r...@localhost.r13151.ovh.net
>> fake...@fakessh.eu fake...@localhost.r13151.ovh.net
>> webm...@fakessh.eu webm...@localhost.r13151.ovh.net
>> se...@fakessh.eu   se...@localhost.r13151.ovh.net
>> @fakessh   r...@localhost.r13151.ovh.net
> 
> fakessh != fakessh.eu.
> you want:
> 
> @fakessh.eu   r...@localhost.r13151.ovh.net
> 
> 

I have but it does not work


hi wieste
is the girl

>> [snip]


Re: catch-all not working with postfix dovecot lda

2010-04-17 Thread mouss
fakessh a écrit :
> On Sat, 17 Apr 2010 14:26:22 +0200, mouss  wrote:
>> fakessh a écrit :
>>> On Thu, 15 Apr 2010 08:33:43 -0500, Noel Jones 
>>> wrote:
 On 4/14/2010 3:42 PM, fakessh wrote:
> On Wed, 14 Apr 2010 13:50:34 -0500, Noel
> Jones
> wrote:
>> On 4/14/2010 1:45 PM, fakessh wrote:
>>> On Wed, 14 Apr 2010 14:12:25 -0400, Charles Marcus
>>>wrote:
> I changed the entries @fakessh to r...@localhost in
>>> /etc/postfix/virtual
> postmap then a file  to
> the postfix restart.
>
> all without success, or rather the same mistake
>>> [snip]
>>> my jed /etc/postfix/virtual
>>> #
>>> # AUTHOR(S)
>>> #Wietse Venema
>>> #IBM T.J. Watson Research
>>> #P.O. Box 704
>>> #Yorktown Heights, NY 10598, USA
>>> #
>>> #
>>> VIRTUAL(5$
>>> postmas...@fakessh.eu   r...@localhost.r13151.ovh.net
>>> fake...@fakessh.eu fake...@localhost.r13151.ovh.net
>>> webm...@fakessh.eu webm...@localhost.r13151.ovh.net
>>> se...@fakessh.eu   se...@localhost.r13151.ovh.net
>>> @fakessh   r...@localhost.r13151.ovh.net
>> fakessh != fakessh.eu.
>> you want:
>>
>> @fakessh.eu  r...@localhost.r13151.ovh.net
>>
>>
> 
> I have but it does not work
> 

it is not in the file you showed.

please show the output of
postmap -q @fakessh.eu hash:/etc/postfix/virtual

after you gather that output, do a new test.


>>> [snip]



Re: DKIM-milter only for outgoing

2010-04-17 Thread mouss
Birta Levente a écrit :
> Hi all
> 
> My postfix server is set up with amavisd-new and dkim-milter.
> 
> In the  main.cf:
> 
> content_filter = smtp-amavis:[127.0.0.1]:10024
> 
> smtpd_milters = inet:localhost:20209
> non_smtpd_milters = inet:localhost:20209
> milter_protocol = 2
> milter_default_action = accept
> 
> 
> 
> With this configuration the DKIM signature is added even to the incoming
> mails and I don't see any reason to do that.
> 
> How can I set up the server to add DKIM signature only for the outgoing
> mails?
> 

you can decide to sign mail based on the domain (and specify different
keys for different domains):

$ cat /path/to/dkim-milter.conf
...
KeyList /path/to/milter-dkim_keylist.conf

$ cat /path/to/milter-dkim_keylist.conf
*:netoyen.net:/path/to/netoyen.net/key
...




> thanks
> 
> Levi
> 
> 
> 



Re: catch-all not working with postfix dovecot lda

2010-04-17 Thread fakessh
On Sat, 17 Apr 2010 17:16:04 +0200, mouss  wrote:
> fakessh a écrit :
>> On Sat, 17 Apr 2010 14:26:22 +0200, mouss  wrote:
>>> fakessh a écrit :
 On Thu, 15 Apr 2010 08:33:43 -0500, Noel Jones

 wrote:
> On 4/14/2010 3:42 PM, fakessh wrote:
>> On Wed, 14 Apr 2010 13:50:34 -0500, Noel
>> Jones
>> wrote:
>>> On 4/14/2010 1:45 PM, fakessh wrote:
 On Wed, 14 Apr 2010 14:12:25 -0400, Charles Marcus
wrote:
>> I changed the entries @fakessh to r...@localhost in
 /etc/postfix/virtual
>> postmap then a file  to
>> the postfix restart.
>>
>> all without success, or rather the same mistake
 [snip]
 my jed /etc/postfix/virtual
 #
 # AUTHOR(S)
 #Wietse Venema
 #IBM T.J. Watson Research
 #P.O. Box 704
 #Yorktown Heights, NY 10598, USA
 #
 #
 VIRTUAL(5$
 postmas...@fakessh.eu   r...@localhost.r13151.ovh.net
 fake...@fakessh.eu fake...@localhost.r13151.ovh.net
 webm...@fakessh.eu webm...@localhost.r13151.ovh.net
 se...@fakessh.eu   se...@localhost.r13151.ovh.net
 @fakessh   r...@localhost.r13151.ovh.net
>>> fakessh != fakessh.eu.
>>> you want:
>>>
>>> @fakessh.eu r...@localhost.r13151.ovh.net
>>>
>>>
>> 
>> I have but it does not work
>> 
> 
> it is not in the file you showed.
> 
> please show the output of
> postmap -q @fakessh.eu hash:/etc/postfix/virtual


to show my output : thanks mouss
[r...@r13151 ~]# postmap -q @fakessh.eu hash:/etc/postfix/virtual
[r...@r13151 ~]# postmap -q @renelacroute.fr hash:/etc/postfix/virtual
[r...@r13151 ~]# postmap -q @fakessh.eu hash:/etc/postfix/virtual
[r...@r13151 ~]# postmap /etc/postfix/virtual
plus postfix restart

log to my error

Apr 17 17:27:02 r13151 postfix/tlsmgr[24186]: open smtp TLS cache
btree:/var/lib/postfix/smtp_tls_session_cache
Apr 17 17:27:02 r13151 postfix/tlsmgr[24186]: tlsmgr_cache_run_event:
start TLS smtp session cache cleanup
Apr 17 17:27:02 r13151 postfix/smtpd[24185]: connect from
smtp28.orange.fr[80.12.242.101]
Apr 17 17:27:02 r13151 postfix/cleanup[24224]: BF607241BC1:
message-id=<20100417152702.bf607241...@r13151.ovh.net>
Apr 17 17:27:03 r13151 postfix/qmgr[24177]: BF607241BC1:
from=, size=254, nrcpt=1 (queue active)
Apr 17 17:27:03 r13151 postfix/error[24225]: BF607241BC1:
to=, relay=none, delay=0.66, delays=0.46/0.21/0/0,
dsn=5.0.0, status=undeliverable (User unknown in virtual alias table)
Apr 17 17:27:03 r13151 postfix/qmgr[24177]: BF607241BC1: removed
Apr 17 17:27:05 r13151 postfix/smtpd[24185]: NOQUEUE: reject: RCPT from
smtp28.orange.fr[80.12.242.101]: 450 4.1.1 : Recipient
address rejected: undeliverable address: User unknown in virtual alias
table; from= to= proto=ESMTP
helo=
Apr 17 17:27:05 r13151 postfix/smtpd[24185]: disconnect from
smtp28.orange.fr[80.12.242.101]


> 
> after you gather that output, do a new test.
> 
> 
 [snip]


Re: catch-all not working with postfix dovecot lda

2010-04-17 Thread fakessh
On Sat, 17 Apr 2010 17:29:04 +0200, fakessh  wrote:
> On Sat, 17 Apr 2010 17:16:04 +0200, mouss  wrote:
>> fakessh a écrit :
>>> On Sat, 17 Apr 2010 14:26:22 +0200, mouss 
wrote:
 fakessh a écrit :
> On Thu, 15 Apr 2010 08:33:43 -0500, Noel Jones
> 
> wrote:
>> On 4/14/2010 3:42 PM, fakessh wrote:
>>> On Wed, 14 Apr 2010 13:50:34 -0500, Noel
>>> Jones
>>> wrote:
 On 4/14/2010 1:45 PM, fakessh wrote:
> On Wed, 14 Apr 2010 14:12:25 -0400, Charles Marcus
>wrote:
>>> I changed the entries @fakessh to r...@localhost in
> /etc/postfix/virtual
>>> postmap then a file  to
>>> the postfix restart.
>>>
>>> all without success, or rather the same mistake
> [snip]
> my jed /etc/postfix/virtual
> #
> # AUTHOR(S)
> #Wietse Venema
> #IBM T.J. Watson Research
> #P.O. Box 704
> #Yorktown Heights, NY 10598, USA
> #
> #   

> VIRTUAL(5$
> postmas...@fakessh.eu   r...@localhost.r13151.ovh.net
> fake...@fakessh.eu fake...@localhost.r13151.ovh.net
> webm...@fakessh.eu webm...@localhost.r13151.ovh.net
> se...@fakessh.eu   se...@localhost.r13151.ovh.net
> @fakessh   r...@localhost.r13151.ovh.net
 fakessh != fakessh.eu.
 you want:

 @fakessh.eur...@localhost.r13151.ovh.net


I have to redo the manipulations. and it works
> 
/etc/postfix/virtual
#
VIRTUAL(5$
postmas...@fakessh.eu   r...@localhost.r13151.ovh.net
fake...@fakessh.eu
fake...@localhost.r13151.ovh.net,r...@localhost.r13151.o$
webm...@fakessh.eu
webm...@localhost.r13151.ovh.net,r...@localhost.r13151.o$
se...@fakessh.eu  
se...@localhost.r13151.ovh.net,r...@localhost.r13151.ovh$
ab...@fakessh.eu   r...@localhost.r13151.ovh.net
postmas...@fakessh   r...@localhost.r13151.ovh.net
renelacro...@renelacroute.fr
renelacro...@localhost.r13151.ovh.net,r...@localho$
postmas...@renelacroute.fr   r...@localhost.r13151.ovh.net
nicolaspic...@nicolaspichot.fr  
nicolaspic...@localhost.r13151.ovh.net,r...@lo$
ab...@nicolaspichot.fr   r...@localhost.r13151.ovh.net
postmas...@nicolaspichot.fr  
r...@localhost.r13151.ovh.net
i...@fakessh.eu r...@localhost.r13151.ovh.net
ca...@fakessh.eu r...@localhost.r13151.ovh.net
r...@fakessh.eu r...@localhost.r13151.ovh.net
f...@fakessh.eu r...@localhost.r13151.ovh.net
@fakessh.eur...@localhost.r13151.ovh.net
@renelacroute.fr   r...@localhost.r13151.ovh.net
@nicolaspichot.fr  r...@localhost.r13151.ovh.net

[r...@r13151 ~]# dovecot -n
# 1.2.11: /etc/dovecot.conf
# OS: Linux 2.6.24.5-grsec--grs-ipv4-32 i686 CentOS release 5.4
(Final) 
base_dir: /var/run/dovecot/
log_timestamp: %Y-%m-%d %H:%M:%S 
protocols: imap imaps pop3 pop3s managesieve
listen(default): [::]
listen(imap): [::]
listen(pop3): [::]
listen(managesieve): *:2000
ssl_listen(default): *:993
ssl_listen(imap): *:993
ssl_listen(pop3): *:995
ssl_listen(managesieve): 
ssl_ca_file: /etc/pki/tls/cert.csr.p12
ssl_cert_file: /etc/pki/tls/newcerts/01.pem
ssl_key_file: /etc/pki/tls/private/r13151.ovh.net.key
version_ignore: yes
login_dir: /var/run/dovecot//login
login_executable(default): /usr/libexec/dovecot/imap-login
login_executable(imap): /usr/libexec/dovecot/imap-login
login_executable(pop3): /usr/libexec/dovecot/pop3-login
login_executable(managesieve): /usr/libexec/dovecot/managesieve-login
mail_location: maildir:~/Maildir:INBOX=~/Maildir/.INBOX
mail_executable(default): /usr/libexec/dovecot/imap
mail_executable(imap): /usr/libexec/dovecot/imap
mail_executable(pop3): /usr/libexec/dovecot/pop3
mail_executable(managesieve): /usr/libexec/dovecot/managesieve
mail_plugins(default): autocreate
mail_plugins(imap): autocreate
mail_plugins(pop3): autocreate
mail_plugins(managesieve): 
mail_plugin_dir(default): /usr/lib/dovecot/imap
mail_plugin_dir(imap): /usr/lib/dovecot/imap
mail_plugin_dir(pop3): /usr/lib/dovecot/pop3
mail_plugin_dir(managesieve): /usr/lib/dovecot/managesieve
imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh
tb-extra-mailbox-sep
imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh
tb-extra-mailbox-sep
imap_client_workarounds(pop3): 
imap_client_workarounds(managesieve): 
pop3_client_workarounds(default): 
pop3_client_workarounds(imap): 
pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh
pop3_client_workarounds(managesieve): 
managesieve_logout_format(default): bytes=%i/%o
managesieve_logout_format(imap): bytes=%i/%o
managesieve_logout_format(pop3): bytes=%i/%o
managesieve_logout_format(managesieve): bytes ( in=%i : out=%o )
lda:
  postmaster_address: postmas...@fa

Re: catch-all not working with postfix dovecot lda

2010-04-17 Thread mouss
fakessh a écrit :
> On Sat, 17 Apr 2010 17:16:04 +0200, mouss  wrote:
>> fakessh a écrit :
>>> On Sat, 17 Apr 2010 14:26:22 +0200, mouss  wrote:
 fakessh a écrit :
> On Thu, 15 Apr 2010 08:33:43 -0500, Noel Jones
> 
> wrote:
>> On 4/14/2010 3:42 PM, fakessh wrote:
>>> On Wed, 14 Apr 2010 13:50:34 -0500, Noel
>>> Jones
>>> wrote:
 On 4/14/2010 1:45 PM, fakessh wrote:
> On Wed, 14 Apr 2010 14:12:25 -0400, Charles Marcus
>wrote:
>>> I changed the entries @fakessh to r...@localhost in
> /etc/postfix/virtual
>>> postmap then a file  to
>>> the postfix restart.
>>>
>>> all without success, or rather the same mistake
> [snip]
> my jed /etc/postfix/virtual
> #
> # AUTHOR(S)
> #Wietse Venema
> #IBM T.J. Watson Research
> #P.O. Box 704
> #Yorktown Heights, NY 10598, USA
> #
> #
> VIRTUAL(5$
> postmas...@fakessh.eu   r...@localhost.r13151.ovh.net
> fake...@fakessh.eu fake...@localhost.r13151.ovh.net
> webm...@fakessh.eu webm...@localhost.r13151.ovh.net
> se...@fakessh.eu   se...@localhost.r13151.ovh.net
> @fakessh   r...@localhost.r13151.ovh.net
 fakessh != fakessh.eu.
 you want:

 @fakessh.eur...@localhost.r13151.ovh.net


>>> I have but it does not work
>>>
>> it is not in the file you showed.
>>
>> please show the output of
>> postmap -q @fakessh.eu hash:/etc/postfix/virtual
> 
> 
> to show my output : thanks mouss
> [r...@r13151 ~]# postmap -q @fakessh.eu hash:/etc/postfix/virtual

so it returns nothing. thus you don't have a line for @fakessh.eu.

Make sure you have
@fakessh   r...@localhost.r13151.ovh.net
in your virtual file.

then postmap the file:
# postmap hash:/etc/postfix/virtual

then run the query again:
# postmap -q @fakessh.eu hash:/etc/postfix/virtual




> [r...@r13151 ~]# postmap -q @renelacroute.fr hash:/etc/postfix/virtual
> [r...@r13151 ~]# postmap -q @fakessh.eu hash:/etc/postfix/virtual
> [r...@r13151 ~]# postmap /etc/postfix/virtual
> plus postfix restart
> 
> [snip]


how to restrict mail to only one recipient?

2010-04-17 Thread Israel Garcia
Hi
I have some apps on a debian server which use to send mail using
localhost on the same server and I want allow only email sent to this
address u...@domain and  reject all other. This is my main.cf

smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no
append_dot_mydomain = no
readme_directory = no

# TLS parameters
smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
smtpd_use_tls=yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache

myhostname = myserver.mydomain
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
myorigin = /etc/mailname
mydestination = myserver.mydomain, localhost.speedyrails.ca, , localhost
smtpd_recipient_restrictions =
check_recipient_access hash:/etc/postfix/recipients,
check_relay_domains,
reject

relayhost = [lbsmtp]
smtp_host_lookup = dns,native
mynetworks = 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = localhost
mailbox_command =
default_transport = smtp
relay_transport = smtp
smtp_host_lookup=dns,native
inet_protocols = ipv4

/etc/postfix/recipient file:

u...@domain  OK
\...@\*  REJECT

So, if I test sending mail using mail command or mutt rules does not
work, but, if I use telnet or nc to connect to localhost on 25/tcp
port rule works. Simple question, WHY?

How can I restrict my server to send mail TO u...@domain?

NOTES:
This server only accept mails from localhost
This server send mails to a load balancer [lbsmtp]

thanks in advance

-- 
Regards;
Israel Garcia


Re: how to restrict mail to only one recipient?

2010-04-17 Thread mouss
Israel Garcia a écrit :
> Hi
> I have some apps on a debian server which use to send mail using
> localhost on the same server and I want allow only email sent to this
> address u...@domain and  reject all other. This is my main.cf
> 
> smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
> biff = no
> append_dot_mydomain = no
> readme_directory = no
> 
> # TLS parameters
> smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
> smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
> smtpd_use_tls=yes
> smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
> smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
> 
> myhostname = myserver.mydomain
> alias_maps = hash:/etc/aliases
> alias_database = hash:/etc/aliases
> myorigin = /etc/mailname
> mydestination = myserver.mydomain, localhost.speedyrails.ca, , localhost
> smtpd_recipient_restrictions =
> check_recipient_access hash:/etc/postfix/recipients,
> check_relay_domains,
> reject
> 
> relayhost = [lbsmtp]
> smtp_host_lookup = dns,native
> mynetworks = 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128
> mailbox_size_limit = 0
> recipient_delimiter = +
> inet_interfaces = localhost
> mailbox_command =
> default_transport = smtp
> relay_transport = smtp
> smtp_host_lookup=dns,native
> inet_protocols = ipv4
> 
> /etc/postfix/recipient file:
> 
> u...@domain  OK
> \...@\*  REJECT

the last line is useless.

> 
> So, if I test sending mail using mail command or mutt rules does not
> work, but, if I use telnet or nc to connect to localhost on 25/tcp
> port rule works. Simple question, WHY?

because smtpd_* parameters apply to mail received via SMTP.

> 
> How can I restrict my server to send mail TO u...@domain?
> 

There are many ways...

[transports]
instead of using smtpd restrictions, you can use transport_maps:

u...@domain smtp:
*   error:recipient address not allowed

(note that '*' only works for transport_maps. don't use it in access maps).

[smtpd restrictions via a content filter]
you can force mail submitted via the sendmail (pickup) interface to go
through smtpd by adding
-o content_filter=smtp:[127.0.0.1]:25

under the "pickup" service in master.cf. However:

- if you do so, you must not use the sendmail command after content
filtering. otherwise, you'll get an infinite loop.

- mail that will be rejected will cause a bounce. you need to handle
this. Instead of "reject", you could use HOLD to put mail on hold (and
remove it manually using the postsuper command), or you can

> NOTES:
> This server only accept mails from localhost
> This server send mails to a load balancer [lbsmtp]
> 
> thanks in advance
> 



Re: how to restrict mail to only one recipient?

2010-04-17 Thread Ansgar Wiechers
On 2010-04-17 Israel Garcia wrote:
> So, if I test sending mail using mail command or mutt rules does not
> work, but, if I use telnet or nc to connect to localhost on 25/tcp
> port rule works. Simple question, WHY?

Because mutt et al. submit their mail via pickup, not via smtpd, and
smtpd_*_restrictions don't apply to pickup.

> How can I restrict my server to send mail TO u...@domain?

# /etc/postfix/main.cf
transport_maps = hash:/etc/postfix/transport

# /etc/postfix/transport
u...@domain   :
* error:destination prohibited

Regards
Ansgar Wiechers
-- 
"Abstractions save us time working, but they don't save us time learning."
--Joel Spolsky


Re: Append a custom head via a filter, partially OT

2010-04-17 Thread mouss
Gary Smith a écrit :
>> Is there some reason the Message-ID won't work as a unique
>> identifier?
>>
> 
> It's about compliance tracking and tagging for specific things.
> 
>> You can use a policy server to insert a header based on
>> envelope information.
>> http://www.postfix.org/SMTPD_POLICY_README.html
>>
>> If your header must be based on the message content, you'll
>> need a milter or content_filter.
>>
> 
> Indeed.  We are hooking into the content_filter as we speak.  We do some 
> analytics on the email message and need to append and track content specific 
> hit ratios for specific messages.  Basically, think of putting a spam score 
> into a message, but instead of checking for spam, we are checking to see if 
> the incoming message violates specific guidelines.  I know it might sound a 
> little trivial as we could just as easily develop some type of database, but 
> since all out email already goes to a compliance archive, we want to keep 
> intact what the hit ratio was for that specific message based upon that point 
> in time without having to worry about keeping some type of mapping in place.  
> (that's the slightly longer reason).

if you're using amavisd-new, then you can write custom code for
amavisd-new.

if not, you can write a spamassassin plugin.

if you want it in shell, then prepend the header, but make sure it is
"valid" (no special characters, ...).




recipient_delimiter is not set

2010-04-17 Thread Jim Carter

Our mailing list situaton is a little different from what normal list
software handles, so I'm trying to roll my own.  I want to use address
extensions to identify the list.  /etc/postfix/main.cf includes only
one instance of:

recipient_delimiter = +

For testing, the user sends to , and in aliases:

testmonkey: listmonkey+testmon...@julia

Then in ~listmonkey/.forward (on Julia):

|$HOME/bin/list-deliver

Then the script takes $EXTENSION as the name of the list.  The script runs,
but reports that $EXTENSION is not set.  Is there something I haven't
turned on?  Evidently so.

I have recipient_delimiter = +  in main.cf, but postconf -d reports that
the variable is empty.  What could be suppressing setting it?

After the output from list-deliver (showing the environment variables) I've
appended the output of postconf -d, followed by main.cf (comments deleted 
due to message size limitations, but the order is authentic). 
The supposedly operative setting of recipient_delimiter is at the end.


James F. Carter  Voice 310 825 2897FAX 310 206 6673
UCLA-Mathnet;  6115 MSA; 405 Hilgard Ave.; Los Angeles, CA, USA 90095-1555
Email: j...@math.ucla.edu  http://www.math.ucla.edu/~jimc (q.v. for PGP key)

-- Forwarded message --
Date: Sat, 17 Apr 2010 17:19:53 -0700 (PDT)
From: Mailing List Special User 
Reply-To: b...@math.ucla.edu
To: j...@math.ucla.edu
Subject: Mail rejected to mailing list ''

Mail (attached below) that you sent to the UCLA Math Department
mailing list '' was not sent out because:
$EXTENSION not set (bug, should have sent to listmonkey+list).

 --- The UCLA Math/PIC Computing Support Group
 

=== Original Message ===

From j...@math.ucla.edu  Sat Apr 17 17:19:53 2010

Return-Path: 
X-Original-To: monkeylist
Delivered-To: monkeyl...@julia.math.ucla.edu
Received: from sunset.math.ucla.edu (sunset.math.ucla.edu [128.97.4.78])
by julia.math.ucla.edu (Postfix) with SMTP id 187405DA7B
for ; Sat, 17 Apr 2010 17:19:29 -0700 (PDT)
To: monkeylist
Subject: Test message to monkeylist

Test message to monkeylist
 DEBUG  Command line:
 DEBUG  Environment variables
CLIENT_ADDRESS=128.97.4.78
CLIENT_HELO=sunset.math.ucla.edu
CLIENT_HOSTNAME=sunset.math.ucla.edu
CLIENT_PROTOCOL=SMTP
DOMAIN=julia.math.ucla.edu
HOME=/u/julia/h1/listmonkey
LANG=C
LOCAL=listmonkey
LOGNAME=listmonkey
MAIL_CONFIG=/etc/postfix
MANPATH=/usr/local/man:/usr/share/man:/usr/X11/man
ORIGINAL_RECIPIENT=monkeylist
PATH=.:/u/julia/h1/listmonkey/bin.i686:/u/julia/h1/listmonkey/bin:/m1/bin:/usr/math/etc:/etc:/usr/local/etc:/usr/math/bin:/usr/local/bin:/bin:/usr/bin:/sbin:/usr/sbin:/usr/bin/X11:/opt/kde3/bin:/opt/kde2/bin:/opt/gnome2/bin:/opt/gnome/bin
PWD=/var/spool/postfix
recipient=listmon...@julia.math.ucla.edu
sender=j...@math.ucla.edu
SHELL=/bin/sh
SHLVL=2
USER=listmonkey
_=/usr/bin/printenv


= Output of postconf -d =

2bounce_notice_recipient = postmaster
access_map_defer_code = 450
access_map_reject_code = 554
address_verify_default_transport = $default_transport
address_verify_local_transport = $local_transport
address_verify_map =
address_verify_negative_cache = yes
address_verify_negative_expire_time = 3d
address_verify_negative_refresh_time = 3h
address_verify_poll_count = 3
address_verify_poll_delay = 3s
address_verify_positive_expire_time = 31d
address_verify_positive_refresh_time = 7d
address_verify_relay_transport = $relay_transport
address_verify_relayhost = $relayhost
address_verify_sender = $double_bounce_sender
address_verify_sender_dependent_relayhost_maps = 
$sender_dependent_relayhost_maps
address_verify_service_name = verify
address_verify_transport_maps = $transport_maps
address_verify_virtual_transport = $virtual_transport
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases, nis:mail.aliases
allow_mail_to_commands = alias, forward
allow_mail_to_files = alias, forward
allow_min_user = no
allow_percent_hack = yes
allow_untrusted_routing = no
alternate_config_directories =
always_add_missing_headers = no
always_bcc =
anvil_rate_time_unit = 60s
anvil_status_update_time = 600s
append_at_myorigin = yes
append_dot_mydomain = yes
application_event_drain_time = 100s
authorized_flush_users = static:anyone
authorized_mailq_users = static:anyone
authorized_submit_users = static:anyone
backwards_bounce_logfile_compatibility = yes
berkeley_db_create_buffer_size = 16777216
berkeley_db_read_buffer_size = 131072
best_mx_transport =
biff = yes
body_checks =
body_checks_size_limit = 51200
bounce_notice_recipient = postmaster
bounce_queue_lifetime = 5d
bounce_service_name = bounce
bounce_size_limit = 5
bounce_template_file =
broken_sasl_auth_clients = no
canonical_classes = envelope_sender, envelope_recipient, header_sender, 
header_recipient
canonical_maps =
cleanup_service_name = cleanup
command_directory = /usr/sbin
command_execution_directory =
command_expansion_filter = 
12345678...@%-_=+:,./abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOP

Re: recipient_delimiter is not set

2010-04-17 Thread Sahil Tandon
On Sat, 17 Apr 2010, Jim Carter wrote:

> I have recipient_delimiter = +  in main.cf, but postconf -d reports that
> the variable is empty.  What could be suppressing setting it?

-d is for DEFAULT. The -n flag is what you use to display non-default
parameter settings.  See the postconf(1) for more information.

-- 
Sahil Tandon