Re: Email in Active Queue without delivery attempts

On Tue, Jun 23, 2009 at 07:57:00PM -0700, Jacky Chan wrote: > > Dear all, > > First thx for your help, I implemented a slow mail queue to yahoo in my > Postfix 2.5.5 installation. > I encountered this issue, some emails to yahoo queued up (just 10 message) > at active queue without delivery atte

Re: Need a resolution to a weird error

At 08:54 PM 6/23/2009, you wrote: Looks as if postifx will not send to mailbox which has close to 50M in the mailbox. Can this be overriden? http://www.postfix.org/postconf.5.html mailbox_size_limit (default: 5120) The maximal size of any local(8) in

Need a resolution to a weird error

Looks as if postifx will not send to mailbox which has close to 50M in the mailbox. Can this be overriden? -- Member - Liberal International This is doc...@nl2k.ab.ca Ici doc...@nl2k.ab.ca God, Queen and country! Beware Anti-Christ rising! Never Satan President Republic! Rudeness is the weak ma

Email in Active Queue without delivery attempts

Dear all, First thx for your help, I implemented a slow mail queue to yahoo in my Postfix 2.5.5 installation. I encountered this issue, some emails to yahoo queued up (just 10 message) at active queue without delivery attempt for 1280. I don't sure why cause it. So I try to manually delivery one

Re: sid-milter with postfix

Hi list sid-milter 1.0.0 work so fine on my box thanks for all your feedbacks > fake...@fakessh.eu wrote: > > I will try to install it correctly ...; > > > > you know a webpage "a sort of how-to" describing the installation, > > documentation clearer than the one ligne on the website postfix >

Re: Blocking with smtpd_client_restrictions

Jon wrote: Sahil Tandon wrote: Show all 'postconf -n' instead of snippets for more thorough debugging. Sorry, figured the shorthand would give enough detail without being too wordy. Here's the rest: mailbox_size_limit = 0 Not recommended. Better to set a really big limit. mydestinati

Re: Blocking with smtpd_client_restrictions

On Tue, 23 Jun 2009, Jon wrote: >> You're trying to block an entire TLD. See the access(5) manual, >> especially the section on lookups from indexed files. You might want >> to try "it" as a lookup key instead of ".it", given the likely >> inclusion of smtpd_access_maps in your configuration

Re: Blocking with smtpd_client_restrictions

Jon wrote: I have postfix on a debian Linux (lenny, ESXi virtual) machine handling inbound traffic for a couple domains on Microsoft Exchange 2003. I am using transport_maps and getadsmtp.pl for my recipient list which seem to work fine. The questions I have are related to smtpd_client_restric

Re: Postifix-v-Spamassassin BLOCK SMTP

EASY steve.h...@digitalcertainty.co.uk wrote, On 6/23/09 11:02 AM: On Tue, 2009-06-23 at 15:52 +0200, Ralf Hildebrandt wrote: * The Doctor: I am contemplating howto use spamassassin effectively with postfix. Usually we use amavisd-new Depends how often you want to keep restarting it. My tim

Re: Postifix-v-Spamassassin BLOCK SMTP

* The Doctor : > Anyway to use the spamassassin headers to reject mail > instead of using amavisd? amavisd-new USES Mail::SpamAssassin

Re: Blocking with smtpd_client_restrictions

Sahil Tandon wrote: Show all 'postconf -n' instead of snippets for more thorough debugging. Sorry, figured the shorthand would give enough detail without being too wordy. Here's the rest: alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases append_dot_mydomain = no biff = no c

Re: Postifix-v-Spamassassin BLOCK SMTP

The Doctor schrieb: > On Tue, Jun 23, 2009 at 08:08:40PM +0200, Ralf Hildebrandt wrote: >> * The Doctor : >> >>> I tried runing amavisd but it is running into weird errors. >> It's the wrong list here, but usually one shows the errors and is >> being helped :) > > > Anyway to use the spamassassin

Re: Blocking with smtpd_client_restrictions

On Jun 23, 2009, at 4:22 PM, Jon wrote: I have postfix on a debian Linux (lenny, ESXi virtual) machine handling inbound traffic for a couple domains on Microsoft Exchange 2003. I am using transport_maps and getadsmtp.pl for my recipient list which seem to work fine. The questions I have ar

Blocking with smtpd_client_restrictions

I have postfix on a debian Linux (lenny, ESXi virtual) machine handling inbound traffic for a couple domains on Microsoft Exchange 2003. I am using transport_maps and getadsmtp.pl for my recipient list which seem to work fine. The questions I have are related to smtpd_client_restrictions. smt

Re: speecify secondary mda behind postfix

On Tue June 23 2009 12:36:19 Victor Duchovni wrote: > > The clean way is to configure your resolver to look at your own DNS > > first, before external queries, then do away with transport_maps > > altogether: > > > > example.com. MX 10 primary.mda.your.domain. > > example.com.

Re: Postifix-v-Spamassassin BLOCK SMTP

The Doctor wrote: On Tue, Jun 23, 2009 at 08:08:40PM +0200, Ralf Hildebrandt wrote: * The Doctor : I tried runing amavisd but it is running into weird errors. It's the wrong list here, but usually one shows the errors and is being helped :) Anyway to use the spamassassin headers to reject

Re: Postifix-v-Spamassassin BLOCK SMTP

On Tue, 2009-06-23 at 20:08 +0200, Ralf Hildebrandt wrote: > * The Doctor : > > > I tried runing amavisd but it is running into weird errors. > > It's the wrong list here, but usually one shows the errors and is > being helped :) If you are running a Debian based distro, this will solve your prob

Re: Postifix-v-Spamassassin BLOCK SMTP

On Tue, Jun 23, 2009 at 08:08:40PM +0200, Ralf Hildebrandt wrote: > * The Doctor : > > > I tried runing amavisd but it is running into weird errors. > > It's the wrong list here, but usually one shows the errors and is > being helped :) Anyway to use the spamassassin headers to reject mail inst

Re: Postifix-v-Spamassassin BLOCK SMTP

* Sahil Tandon : > Noel are you suggesting something might not work for me because I don't > know how to use it? Blasphemer! Sigged.

Re: Postifix-v-Spamassassin BLOCK SMTP

* Wietse Venema : > Perhaps there a case of name confusion. There are several tools > that have "amavis" in the name. The one that reportedly works well > with Postfix is called "amavisd-new". Well, the other project are dead, really. amavis is nowadays synonym for Mark^h^h^h^hamavisd-new. Anyw

Re: Postifix-v-Spamassassin BLOCK SMTP

* The Doctor : > I tried runing amavisd but it is running into weird errors. It's the wrong list here, but usually one shows the errors and is being helped :)

Re: speecify secondary mda behind postfix

On Tue, Jun 23, 2009 at 11:54:07AM -0500, /dev/rob0 wrote: > On Tue June 23 2009 06:32:26 Ji Hlinka wrote: > > Define secodnary MX record for the secondary MDA is one of a > > posiibilities > > > > :-), but i still hope there is simpler solution, something like > > : adding > > > > another IP

Re: Postifix-v-Spamassassin BLOCK SMTP

On Tue, 2009-06-23 at 11:50 -0500, Noel Jones wrote: > Sahil Tandon wrote: > > Noel are you suggesting something might not work for me because I don't > > know how to use it? Blasphemer! > > ;-) > Next I'll ask you about painting my bike shed... How dare you waste a shed on Bikes! I would fill i

Re: Postifix-v-Spamassassin BLOCK SMTP

On Tue, 2009-06-23 at 18:59 +0200, Benny Pedersen wrote: > On Tue, June 23, 2009 18:46, Steve wrote: > > I am assured that it is amavis-new :-) However, I've also been told the > > lottery numbers over and over and I've not won a penny. > > well you need to play if you want to win, admins like me

Re: Postifix-v-Spamassassin BLOCK SMTP

On Tue, June 23, 2009 18:46, Steve wrote: > I am assured that it is amavis-new :-) However, I've also been told the > lottery numbers over and over and I've not won a penny. well you need to play if you want to win, admins like me get fingers very dirthy one or more times, but for me its the road

Re: speecify secondary mda behind postfix

On Tue June 23 2009 06:32:26 Jiří Hlinka wrote: > Define secodnary MX record for the secondary MDA is one of a > posiibilities > > :-), but i still hope there is simpler solution, something like > : adding > > another IP (the IP of secondary MDA) on each line of transport_maps > :-). > > Im little

Re: Postifix-v-Spamassassin BLOCK SMTP

Sahil Tandon wrote: Noel are you suggesting something might not work for me because I don't know how to use it? Blasphemer! ;-) Next I'll ask you about painting my bike shed... But enough of this. While I appreciate that Steve had a bad experience with amavisd-new, my point is that many, man

Re: Postifix-v-Spamassassin BLOCK SMTP

On Tue, 2009-06-23 at 12:38 -0400, Wietse Venema wrote: > EASY steve.h...@digitalcertainty.co.uk: > > Had I have been a Barracuda developer I would have asked for advice. I > > was not. Me just a low grade tech support droid having to restart amavis > > Perhaps there a case of name confusion. The

Re: Postifix-v-Spamassassin BLOCK SMTP

EASY steve.h...@digitalcertainty.co.uk: > Had I have been a Barracuda developer I would have asked for advice. I > was not. Me just a low grade tech support droid having to restart amavis Perhaps there a case of name confusion. There are several tools that have "amavis" in the name. The one that

Re: Postifix-v-Spamassassin BLOCK SMTP

On Jun 23, 2009, at 12:08 PM, Noel Jones wrote: EASY steve.h...@digitalcertainty.co.uk wrote: On Tue, 2009-06-23 at 15:52 +0200, Ralf Hildebrandt wrote: * The Doctor : I am contemplating howto use spamassassin effectively with postfix. Usually we use amavisd-new Depends how often you want

Re: Postifix-v-Spamassassin BLOCK SMTP

On Tue, 2009-06-23 at 11:08 -0500, Noel Jones wrote: > EASY steve.h...@digitalcertainty.co.uk wrote: > > On Tue, 2009-06-23 at 15:52 +0200, Ralf Hildebrandt wrote: > >> * The Doctor : > >> > >>> I am contemplating howto use spamassassin effectively with postfix. > >> Usually we use amavisd-new > >

Re: Postifix-v-Spamassassin BLOCK SMTP

EASY steve.h...@digitalcertainty.co.uk wrote: On Tue, 2009-06-23 at 15:52 +0200, Ralf Hildebrandt wrote: * The Doctor : I am contemplating howto use spamassassin effectively with postfix. Usually we use amavisd-new Depends how often you want to keep restarting it. My time at Barracuda taugh

Re: speecify secondary mda behind postfix

Ji?? Hlinka: > Hi Wietse, > thank you for your answer. Specify multiple IP for one domain name > semms a bit tricky to me, so i'll go the way described by Jarek (set > up local MX records). > > two more questions :-): > 1) as described in Postfix Documentation, the "transport_maps", where > is def

Re: speecify secondary mda behind postfix

Hi Wietse, thank you for your answer. Specify multiple IP for one domain name semms a bit tricky to me, so i'll go the way described by Jarek (set up local MX records). two more questions :-): 1) as described in Postfix Documentation, the "transport_maps", where is defined something like: domain.t

Re: Postifix-v-Spamassassin BLOCK SMTP

On Tue, 2009-06-23 at 15:52 +0200, Ralf Hildebrandt wrote: > * The Doctor : > > > I am contemplating howto use spamassassin effectively with postfix. > > Usually we use amavisd-new Depends how often you want to keep restarting it. My time at Barracuda taught me to steer clear of Amavis. 'Captain

Re: Postifix-v-Spamassassin BLOCK SMTP

On Tue, Jun 23, 2009 at 03:52:15PM +0200, Ralf Hildebrandt wrote: > * The Doctor : > > > I am contemplating howto use spamassassin effectively with postfix. > > Usually we use amavisd-new I tried runing amavisd but it is running into weird errors. -- Member - Liberal International This is do

Re: Postifix-v-Spamassassin BLOCK SMTP

* The Doctor : > I am contemplating howto use spamassassin effectively with postfix. Usually we use amavisd-new

Re: Postifix-v-Spamassassin BLOCK SMTP

On Tue, Jun 23, 2009 at 09:21:52AM +0100, Steve wrote: > Silly question. Currently I have Postfix using Spamassassin as a content > filter thus; > > smtp inet n - - - 10 smtpd > -o content_filter=spamassassin > ... > spamassassin unix - n n

Re: Postifix-v-Spamassassin BLOCK SMTP

EASY steve.h...@digitalcertainty.co.uk wrote, at 06/23/2009 09:12 AM: > Joey wrote: >>> Actually, I use a header_checks rule: >>> >>> /X-Spam-Level: \*{5,}/ REJECT > > I wrote; >> I looked at this myself and asked 'hang on, what if I put a header >> filter in for X-Spam-Level'. I assumed (and tha

Re: Postifix-v-Spamassassin BLOCK SMTP

Joey wrote: > > > > Actually, I use a header_checks rule: > > > > /X-Spam-Level: \*{5,}/ REJECT I wrote; > I looked at this myself and asked 'hang on, what if I put a header > filter in for X-Spam-Level'. I assumed (and that is all it was) that it > was not fed into the content filter until *af

Re: Postifix-v-Spamassassin BLOCK SMTP

On Tue, 2009-06-23 at 08:51 -0400, Jorey Bump wrote: > Steve wrote, at 06/23/2009 04:21 AM: > > Silly question. Currently I have Postfix using Spamassassin as a content > > filter thus; > > > > smtp inet n - - - 10 smtpd > > -o content_filter=spamassass

Re: Postifix-v-Spamassassin BLOCK SMTP

Steve wrote, at 06/23/2009 04:21 AM: > Silly question. Currently I have Postfix using Spamassassin as a content > filter thus; > > smtp inet n - - - 10 smtpd > -o content_filter=spamassassin > ... > spamassassin unix - n n - -

Re: rejecting client=unknown[ip.ad.dr.ess]

LuKreme wrote, at 06/23/2009 02:58 AM: > On 22-Jun-2009, at 18:29, mouss wrote: >>> Is there anyway to, if not outright reject anyone whose DNS shows up as >>> unknown to at least tempfail them with a "Ooops, your DNS is not >>> resolving, try back later" or something? > >> if you insist, you coul

Re: rejecting client=unknown[ip.ad.dr.ess]

LuKreme schrieb: > On 22-Jun-2009, at 18:29, mouss wrote: >>> Is there anyway to, if not outright reject anyone whose DNS shows up as >>> unknown to at least tempfail them with a "Ooops, your DNS is not >>> resolving, try back later" or something? > >> if you insist, you could use one of >> >> http

Re: speecify secondary mda behind postfix

Ji?? Hlinka: > Hi Jarek, > thanks for fast reply! > Define secodnary MX record for the secondary MDA is one of a posiibilities > :-), but i still hope there is simpler solution, something like adding > another IP (the IP of secondary MDA) on each line of transport_maps :-). The transport_maps take

Re: speecify secondary mda behind postfix

Hi Jarek, thanks for fast reply! Define secodnary MX record for the secondary MDA is one of a posiibilities :-), but i still hope there is simpler solution, something like adding another IP (the IP of secondary MDA) on each line of transport_maps :-). Im little bit afraid of MX record solution (al

Re: speecify secondary mda behind postfix

Jiří Hlinka wrote: Hello, i have this situation: Postfix server acts as relay for Lotus Domino (MDA) and everything works ok. Customer adds another Domino server because of HA. The second Domino server has different IP. Delivery process is obvious: when there is not available "primary" Domino

speecify secondary mda behind postfix

Hello, i have this situation: Postfix server acts as relay for Lotus Domino (MDA) and everything works ok. Customer adds another Domino server because of HA. The second Domino server has different IP. Delivery process is obvious: when there is not available "primary" Domino server, send everything

warning: maildir access problem for UID/GID=4444/4444: create maildir file

When i send a mail to local postfix installation, i get error Jun 23 16:13:22 linux postfix/virtual[2526]: warning: maildir access problem for UID/GID=/: create maildir file /home/vmail/info/tmp/1245753802.P2526.linux.localdomain: Permission denied I have set vmail ownership and also set pe

RE: Postifix-v-Spamassassin BLOCK SMTP

On Tue, 2009-06-23 at 13:00 +0300, Dudi Goldenberg wrote: > >The reason I ask is this bounce; > > > >... > >: host mail.varna.net[217.145.80.1] said: 550 5.7.1 > >Blocked by SpamAssassin (in reply to end of DATA command) > > This is Spamassassin milter in action. > > Consult your distribution rep

RE: Postifix-v-Spamassassin BLOCK SMTP

>The reason I ask is this bounce; > >... >: host mail.varna.net[217.145.80.1] said: 550 5.7.1 >Blocked by SpamAssassin (in reply to end of DATA command) This is Spamassassin milter in action. Consult your distribution repository or have a look at: http://savannah.nongnu.org/projects/spamass-milt/

Postifix-v-Spamassassin BLOCK SMTP

Silly question. Currently I have Postfix using Spamassassin as a content filter thus; smtp inet n - - - 10 smtpd -o content_filter=spamassassin ... spamassassin unix - n n - - pipe user=spamd argv=/usr/bin/spamc -f -e