On Sat, 18 Jul 2009, ram wrote:
We run smtp services for our clients using smtp-auth. And nowadays we
also enforce a strong password (minimum alphanumeric)
But still people's passwords get compromised. Even a relatively strong
password. To save our postfix servers I have implemented rate-limits
i always see in the postfix maillog the following:
dsn=2.6.0,dsn=2.0.0,dsn=4.0.0,
understand this is the status of the delivery; what is the significance of
these numbers after dsn?; (e.g. dsn=2.0.0 i understand status sent ok) i
googled for it but could not manage to get any info about this;
som
Jumping Mouse a écrit :
> Hello everyone,
>
> I am using postfix 2.5.4 with amavisd-new, courier imap, clamd,
> spamassasin, maildrop on Ubuntu 6.06.2 LTS server which I inherited.
>
> I have been struggling alone to try to resolve two issues and hope that
> i can get some help here.
when you
Charles Sprickman a écrit :
> Hello all,
>
> We've been using vpopmail+qmail for the past 6 years or so, and need to
> deploy new hardware. I'm seriously considering a move to something more
> modern on the software side. Vpopmail has worked well for us, but it's
> a bit hackish, as is the bundl
Hello,
Just out of curiosity how do you let your users change their passwords?
2009/7/18 Charles Sprickman :
> On Sat, 18 Jul 2009, ram wrote:
>
>> We run smtp services for our clients using smtp-auth. And nowadays we
>> also enforce a strong password (minimum alphanumeric)
>> But still people's
Ok thanks mouss willl split this message into two requests
1. smtp time outs and delays
2. spamc being called when using amavis-new
and close this message... so everyone please consider this message closed it
will will be continued with subjects "smtp time outs and delays" and "spamc
being ca
solution proposed by mouss:
remove: this line:xfilter "/usr/bin/spamc"from maildroprc
I am noticing the following in the mail logs:
Jul 17 06:18:42 mail spamc[32239]: connect(AF_INET) to spamd at 127.0.0.1
failed, retrying (#1 of 3): Connection refusedJul 17 06:18:43 mail
spamc[32239]
>solution proposed by mouss:
>remove: this line:xfilter "/usr/bin/spamc"from maildroprc
I see that this that having this line in maildroprc can cause a delay of
about 5 seconds per email message, could this have been causing major delays
in delivery during high server load
K bharathan:
> i always see in the postfix maillog the following:
>
> dsn=2.6.0,dsn=2.0.0,dsn=4.0.0,
>
> understand this is the status of the delivery; what is the significance of
> these numbers after dsn?; (e.g. dsn=2.0.0 i understand status sent ok) i
> googled for it but could not manage to g
continued from "smtp time outs and delays + spamc being called when using
amavis-new"
mouss wrote:
"hard to tell, but a first bet is reverse DNS lookup. if the clients use
a private IP space, make sure your DNS server answers for thecorresponding
reverse zone so that postfix gets an NXDOMAIN qui
On 7/18/2009, mouss (mo...@ml.netoyen.net) wrote:
>> -Continued use of Courier-IMAP. Not so much because I like it, but I
>> don't want POP UUIDs changing or any big changes in IMAP quirks that
>> suddenly cause users grief. It seems like Courier+Maildrop is fairly
>> common though, so I think I'
On Sat, 18 Jul 2009, Charles Marcus wrote:
Oh... and although I did recommend moving to dovecot, if all you use is
POP, and there is no chance you will be switching to IMAP, then it I
don't think you'd see any benefit switching to dovecot...
Except the performance increase under Dovecot is 30
Thanks again mouss.
most of my users are in an office network behind a firewall and are using an
ms server 2003 dns for local lookups my isp's dns server for non local
lookups. My ISP is also hosting the dns records for the postfix server.
How can I test if postfix is getting an NXDOMAIN quic
On 7/18/2009, Jumping Mouse (kafr...@hotmail.com) wrote:
> Here is my main.cf
>
> # Postfix master process configuration file. For details on the format
postconf -n output only please...
--
Best regards,
Charles
On 7/18/2009, Res (r...@ausics.net) wrote:
> > Oh... and although I did recommend moving to dovecot, if all you use is
> > POP, and there is no chance you will be switching to IMAP, then it I
> > don't think you'd see any benefit switching to dovecot...
>
> Except the performance increase under Do
Here is my postconf -n output:
~$ postconf -nalias_maps = hash:/etc/aliases,
hash:/var/lib/mailman/data/aliasesbiff = nobroken_sasl_auth_clients =
yesconfig_directory = /etc/postfixcontent_filter =
smtp-amavis:[127.0.0.1]:10024delay_warning_time = 4hhome_mailbox =
Maildir/ignore_mx_lookup_err
On Sat, 18 Jul 2009, Charles Marcus wrote:
> On 7/18/2009, Res (r...@ausics.net) wrote:
> > > Oh... and although I did recommend moving to dovecot, if all you use is
> > > POP, and there is no chance you will be switching to IMAP, then it I
> > > don't think you'd see any benefit switching to dove
On 7/18/2009, Sahil Tandon (sa...@tandon.net) wrote:
> Just so I understand, you don't use POP3 on the server you manage;
> you have never compared POP3 performance on Dovecot vs.
> $something_else, but you are commenting on the lack of performance
> benefit? :)
Only because I've been on the dove
On Sat, 18 Jul 2009, Charles Marcus wrote:
> On 7/18/2009, Sahil Tandon (sa...@tandon.net) wrote:
> > Just so I understand, you don't use POP3 on the server you manage;
> > you have never compared POP3 performance on Dovecot vs.
> > $something_else, but you are commenting on the lack of performan
On 7/18/2009 11:23 AM, Sahil Tandon wrote:
>>> See: http://wiki.dovecot.org/POP3Server
>> Yep, seems to say something similar...
> What's with all the ellipses?! Finish your thought! :)
Ok, I'll try... ;)
thnks
On Sat, Jul 18, 2009 at 2:20 PM, Wietse Venema wrote:
> K bharathan:
> > i always see in the postfix maillog the following:
> >
> > dsn=2.6.0,dsn=2.0.0,dsn=4.0.0,
> >
> > understand this is the status of the delivery; what is the significance
> of
> > these numbers after dsn?; (e.g. dsn=2.
Jumping Mouse a écrit :
> Thanks again mouss.
>
> most of my users are in an office network behind a firewall and are
> using an ms server 2003 dns for local lookups my isp's dns server for
> non local lookups. My ISP is also hosting the dns records for the
> postfix server.
>
> How can I test
gianluca...@interfree.it a écrit :
> Hi
>
>
> My mailserver store mail in Maildir format, is possible through postfix,
> mailscanner or procmail to store mail with subject filename so i can find
> mail more quicly on server?
>
>
the subject is a bad choice for a filename:
- the filename mus
On Jul 18, 2009, at 4:38 AM, Damian Myerscough wrote:
Hello,
Just out of curiosity how do you let your users change their
passwords?
Adding to this, do you have a forgot password feature that perhaps
gives them passwords to a master control panel of some form?
Did you distribute their
LuKreme:
> Getting a lot of these:
>
> postfix/trivial-rewrite[88525]: fatal: proxy:mysql:/usr/local/etc/
> postfix/mysql_virtual_domains_maps.cf(0,lock|fold_fix): table lookup
> problem
Log for trivial-rewrite warning: records in Postfix logs.
Look in the MySQL logs.
Wietse
Hi there,
I am using fetchmail to pop3 mail from gmail. But when I receive email
I find that fetchmail is using postfix to deliver the mail to the
corresponding internal mailbox. postfix responds with the following
error and best I can tell the mail never ends up in my inbox. Looks
like lo
Getting a lot of these:
postfix/trivial-rewrite[88525]: fatal: proxy:mysql:/usr/local/etc/
postfix/mysql_virtual_domains_maps.cf(0,lock|fold_fix): table lookup
problem
postfix/smtpd[27380]: warning: problem talking to service rewrite:
Unknown error: 0
postfix/smtpd[27362]: warning: problem t
Weitse:
LuKreme:
> Getting a lot of these:
>
> postfix/trivial-rewrite[88525]: fatal: proxy:mysql:/usr/local/etc/
> postfix/mysql_virtual_domains_maps.cf(0,lock|fold_fix): table lookup
> problem
Log for trivial-rewrite warning: records in Postfix logs.
Look in the MySQL logs.
Despite my.cfg ha
On 18-Jul-2009, at 22:43, LuKreme wrote:
Weitse:
LuKreme:
> Getting a lot of these:
OK, never mind. After digging through the thousands of log lines I
found the first sql error.
Evidently at some point in updating postfixadmin the password to the
'postfix' mysql database was changed to '
On Sat, 18 Jul 2009, LuKreme wrote:
> Weitse:
>> LuKreme:
>> > Getting a lot of these:
>> >
>> > postfix/trivial-rewrite[88525]: fatal: proxy:mysql:/usr/local/etc/
>> > postfix/mysql_virtual_domains_maps.cf(0,lock|fold_fix): table lookup
>> > problem
>>
>> Log for trivial-rewrite warning: records
30 matches
Mail list logo
