headers
Julian Cowley | 1 Jul 2008 03:44
Favicon

Re: Auto Response

On Mon, 30 Jun 2008, mouss wrote:
> Brent Bice wrote:
>>     One thing you might consider is that most auto-responders respond to
>>  things they shouldn't (viruses, spam, mailing lists, etc) and this often
>>  irritates people.  On a cyrus server, you can use sieve to do server-side
>>  filtering and/or auto-responses. I've used the squirrelmail plugin for
>>  sieve to configure vacation auto-responders and one nice side-effect is
>>  that you can configure things so that sieve doesn't auto-respond to email
>>  messages from mailing lists - a step in the right direction.
>>
>>     I have no idea if dovecot has anything like sieve or not - I've never
>>  used dovecot and don't know a thing about it.
>
> dovecot has dovecot-sieve (not all features are available at this time, but 
> it's ongoing). but I have never used its vacation part.

It works fine, but be sure to use the latest version.  Some refinements
to the RFC 3834 guidelines (don't respond to mailing lists, etc.) are
only in version dovecot-sieve 1.0.3 onwards.

http://www.dovecot.org/releases/sieve/dovecot-sieve-1.0.3.tar.gz
Permalink | Reply | 0 comments |
headers
kemas henry | 1 Jul 2008 06:28
Picon

queue file size limit exceeded

what is "queue file size limit exceeded" error means?
    Jul  1 08:58:02 webmail postfix/smtpd[20392]: warning: 98F9AE0088: 
queue file size limit exceeded
I see it several time in my logs, is it something that should be worried 
about ?

below is my postconf -n output

alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases, ldap:/etc/postfix/ldap-aliases
allow_min_user = yes
allow_percent_hack = yes
append_at_myorigin = no
append_dot_mydomain = yes
biff = no
broken_sasl_auth_clients = yes
command_directory = /usr/sbin
config_directory = /etc/postfix
daemon_directory = /usr/libexec/postfix
data_directory = /var/lib/postfix
default_privs = nobody
default_process_limit = 1000
delay_warning_time = 4h
disable_vrfy_command = yes
empty_address_recipient = MAILER-DAEMON
home_mailbox = Maildir/
html_directory = no
inet_interfaces = all
local_recipient_maps = $alias_maps
mail_owner = postfix
(Continue reading)

Permalink | Reply | 2 comments |
headers
Magnus Bäck | 1 Jul 2008 07:08
Picon
Picon
Favicon

Re: queue file size limit exceeded

On Tuesday, July 01, 2008 at 06:28 CEST,
     kemas henry <kemas.henry <at> ramayana.co.id> wrote:

> what is "queue file size limit exceeded" error means?
>    Jul  1 08:58:02 webmail postfix/smtpd[20392]: warning: 98F9AE0088: 
> queue file size limit exceeded
> I see it several time in my logs, is it something that should be
> worried about ?

It's probably because some client has attempted to send a message that
exceeds $message_size_limit.

[...]

> append_at_myorigin = no

This is not supported. Set it back to the default value.

http://www.postfix.org/postconf.5.html#append_at_myorigin

[...]

--

-- 
Magnus Bäck
magnus <at> dsek.lth.se
Permalink | Reply | 1 comment |
headers
kemas henry | 1 Jul 2008 07:02
Picon

Re: queue file size limit exceeded

Magnus Bäck wrote:
> On Tuesday, July 01, 2008 at 06:28 CEST,
>      kemas henry <kemas.henry <at> ramayana.co.id> wrote:
>
>   
>> what is "queue file size limit exceeded" error means?
>>    Jul  1 08:58:02 webmail postfix/smtpd[20392]: warning: 98F9AE0088: 
>> queue file size limit exceeded
>> I see it several time in my logs, is it something that should be
>> worried about ?
>>     
>
> It's probably because some client has attempted to send a message that
> exceeds $message_size_limit.
>
> [...]
>
>   

so no need to worry about, right?

>> append_at_myorigin = no
>>     
>
> This is not supported. Set it back to the default value.
>
> http://www.postfix.org/postconf.5.html#append_at_myorigin
>
> [...]
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Daniel Chojecki | 1 Jul 2008 09:18
Picon

Re: Recipient limit, need advice

2008/6/30 mouss <mouss <at> netoyen.net>:

> spamfilter_destination_recipient_limit = 1

i have set above parameter and still not working
as expected.

I have checked spamassasin logs and i can see that
"To:" field still contains two addresses.

Any idea ?

--

-- 
Best Regards,
Daniel Chojecki
Permalink | Reply | 4 comments |
headers
Nicolas Letellier | 1 Jul 2008 09:26
Favicon

Re: backupmx with Postfix

On Mon, 30 Jun 2008 21:33:21 +0200
mouss <mouss <at> netoyen.net> wrote:
> > I receive many many emails (and only spam, it seems). Is it normal? I thinked that my mail server would be
used only if smtp.domain.com be down. Why not?
> >
> > See a log:
> > Jun 30 15:34:47 trinite postfix/pipe[74027]: BF9E73228973: to=<newton <at> domain.com>,
relay=my_service, delay=1.8, delays=1.7/0/0/0.04, dsn=2.0.0, status=sent (delivered via
my_service service)
> > Jun 30 15:34:48 trinite postfix/smtp[74990]: DF5023228976: to=<newton <at> domain.com>,
relay=smtp.domain.com[**.**.**.**]:25, delay=0.48, delays=0.01/0/0.11/0.36, dsn=2.0.0,
status=sent (250 2.0.0 m5UDYlX4030260 Message accepted for delivery)
> >
> > I don't know why I have two lines... 
> 
> I hope that you have more than two lines: there should be a 
> postfix/smtpd (with a 'd' at the end) in your logs for these transaction 
> attempts.
Yes, I have the 'smtpd' line, of course. I juste pasted the two lines where I have a question. Is it normal tha
the mail to relay pass by my service (from master.cf), and after, is sent by smtp.domain.com.
I thinked than the mail to relay will just pass directly by the relay, not by the service.

Another question:
I see that bounce mail could be problematic. Is it a good idea (and mainly, is it possible?) to disable bounce
mail *only* for mail to relay?

One another:
Is it adviced to reject mail with a sender address not resolvable?

Thanks.
(Continue reading)

Permalink | Reply | 11 comments |
headers
mouss | 1 Jul 2008 10:32
Favicon

Re: Recipient limit, need advice

Daniel Chojecki wrote:
> 2008/6/30 mouss <mouss <at> netoyen.net>:
>
>   
>> spamfilter_destination_recipient_limit = 1
>>     
>
> i have set above parameter and still not working
> as expected.
>
> I have checked spamassasin logs and i can see that
> "To:" field still contains two addresses.
>
> Any idea ?
>
>   

then change your spamfilter (it is a script I guess) to print its 
command lines args ($ <at> ) to a file so that you can look at them.

any reason why you don't use amavisd-new?
Permalink | Reply | 0 comments |
headers
mouss | 1 Jul 2008 10:41
Favicon

Re: backupmx with Postfix

Nicolas Letellier wrote:
> [snip]
> Yes, I have the 'smtpd' line, of course. I juste pasted the two lines where I have a question. Is it normal tha
the mail to relay pass by my service (from master.cf), and after, is sent by smtp.domain.com.
> I thinked than the mail to relay will just pass directly by the relay, not by the service.
>   

What do you mean by "service" vs "relay"? mail is queued by the relay 
server and then sent to the final destination (provided the relay server 
is not configured to deliver such mail locally).
> Another question:
> I see that bounce mail could be problematic. Is it a good idea (and mainly, is it possible?) to disable
bounce mail *only* for mail to relay?
>
>   

you should make sure that you validate recipients during the smtp 
transaction. so either have the list of relay recipients 
(relay_recipient_maps) or use reject_unverified_recipient (but the 
latter breaks the purpose of "backup" in backupMX :).

> One another:
> Is it adviced to reject mail with a sender address not resolvable?
>   

you can but it does not catch a a lot of junk. use zen.spamhaus.org and 
after that see what spam is missed. you can then tune your restrictions 
if possible (otherwise, use a content filter).
(Continue reading)

Permalink | Reply | 10 comments |
headers
Nicolas Letellier | 1 Jul 2008 10:48
Favicon

Re: backupmx with Postfix

On Tue, 01 Jul 2008 10:41:10 +0200
mouss <mouss <at> netoyen.net> wrote:
> > Another question:
> > I see that bounce mail could be problematic. Is it a good idea (and mainly, is it possible?) to disable
bounce mail *only* for mail to relay?
> 
> you should make sure that you validate recipients during the smtp 
> transaction. so either have the list of relay recipients 
> (relay_recipient_maps) or use reject_unverified_recipient (but the 
> latter breaks the purpose of "backup" in backupMX :).
Yes, I use a recipient_maps. But if I receive a mail for a bas recipient, by postfix will send a bounce to the
sender to notify the mail does not exist (and it can be problematic if the send address does not exist).

--

-- 
 -Nicolas.
Permalink | Reply | 9 comments |
headers
mouss | 1 Jul 2008 11:04
Favicon

Re: backupmx with Postfix

Nicolas Letellier wrote:
> On Tue, 01 Jul 2008 10:41:10 +0200
> mouss <mouss <at> netoyen.net> wrote:
>   
>>> Another question:
>>> I see that bounce mail could be problematic. Is it a good idea (and mainly, is it possible?) to disable
bounce mail *only* for mail to relay?
>>>       
>> you should make sure that you validate recipients during the smtp 
>> transaction. so either have the list of relay recipients 
>> (relay_recipient_maps) or use reject_unverified_recipient (but the 
>> latter breaks the purpose of "backup" in backupMX :).
>>     
> Yes, I use a recipient_maps. But if I receive a mail for a bas recipient, by 

s/bas/bad ?

> postfix will send a bounce to the sender to notify the mail does not exist 

If you have relay_recipient_maps set, then postfix will _reject_, not 
bounce. it is the "previous" MTA that generates the bounce. This is why 
you should reject on the first server that you manage and let others 
bounce or do whatever they want.

> (and it can be problematic if the send address does not exist).
>   

if the sender does not exist, there is not much problems. The real 
problem is if the sender exists but did not send the message (spam 
forges sender address) and when you as a victim get thousands of NDRs
(Continue reading)

Permalink | Reply | 8 comments |

Gmane