D G Teed:
> So, this is an uncontrollable setting. The response from
> host not found should be something we can configure,
> not hardwired to defer.
Postfix handles "host does not exist" as a permanent error.
Postfix handles "no DNS reply" as a non-permanent error.
It is a mistake to handle "n
Am 19.12.2009 00:07, schrieb Dasza Seyda:
> If I add a "relayhost" to main.cf:
>
> relayhost = relayhost.example.com
>
> all main will be delivered through relayhost.example.com.
>
>
>
> Now, I would like to deliver mail i.e. for @mylocaldomain directly,
> not through relayhost - how should I do it
On Fri, Dec 18, 2009 at 4:41 PM, Noel Jones wrote:
> On 12/18/2009 2:14 PM, D G Teed wrote:
>
>> We have an smtp outbound-only service on postfix.
>> Users on exchange are relayed out through this.
>>
>> Once in awhile someone has a typo in their domain name.
>> Postfix bounces it back to exchang
If I add a "relayhost" to main.cf:
relayhost = relayhost.example.com
all main will be delivered through relayhost.example.com.
Now, I would like to deliver mail i.e. for @mylocaldomain directly, not
through relayhost - how should I do it?
I tried sender_dependent_relayhost_maps, but I'm no
On Fri, Dec 18, 2009 at 5:41 PM, Noel Jones wrote:
> "postconf -d" shows built-in defaults, not the settings currently used. For
> current settings, use "postconf".
Woops.
> These are temporary errors that postfix rightfully keeps in the queue. A
> computer can't tell the difference between a
Hi!,
Try Postfix quota reject it sais at the reject moment wich users are over quota
and the sender can easily know whose of the users should remove from the
recipient list for the mail to be able to be sent. It's comfortable, scalable
and IMHO works nice...
Bye!!
http://postfixquotareject.ra
On 12/18/2009 4:15 PM, Carlos Williams wrote:
On Fri, Dec 18, 2009 at 5:01 PM, Aaron Wolfe wrote:
I think you might be trying to solve the wrong problem. Why queue
mail for destinations that don't have MX records (typoed domain part,
etc)? Better to return undeliverable to senders I would thi
On 12/18/2009 4:08 PM, Cameron Smith wrote:
On Fri, Dec 18, 2009 at 12:50 PM, Noel Jones wrote:
On 12/18/2009 2:34 PM, Cameron Smith wrote:
The mail server for something.com has been changed to
mail.somethingelse.com
It's working fine for regular mail through a client.
Scripts (Drupal) on s
On Fri, Dec 18, 2009 at 5:01 PM, Aaron Wolfe wrote:
> I think you might be trying to solve the wrong problem. Why queue
> mail for destinations that don't have MX records (typoed domain part,
> etc)? Better to return undeliverable to senders I would think. This
> is different than mail to domai
On Fri, Dec 18, 2009 at 12:50 PM, Noel Jones wrote:
> On 12/18/2009 2:34 PM, Cameron Smith wrote:
>>
>> The mail server for something.com has been changed to
>> mail.somethingelse.com
>>
>> It's working fine for regular mail through a client.
>>
>> Scripts (Drupal) on something.com when sending em
On Fri, Dec 18, 2009 at 3:25 PM, Carlos Williams wrote:
> I notice from time to time by checking my mail queue that messages get
> stuck there because users send to an invalid or non existing domain.
> My Postfix server attempts to hold the message in queue for later
> delivery assuming the remote
Hi,
I've been running Postfix/MySQL/Courier for months with no problems.
Suddenly in the last day or so, mail has been taking around 3 hours to
process. I don't have a clue where to start looking. When I do a qshape, I
see this:
T 5 10 20 40 80 160 320
On 12/18/2009 2:34 PM, Cameron Smith wrote:
The mail server for something.com has been changed to mail.somethingelse.com
It's working fine for regular mail through a client.
Scripts (Drupal) on something.com when sending email though are failing.
How do I modify main.cf for the postfix install
On 12/18/2009 2:14 PM, D G Teed wrote:
We have an smtp outbound-only service on postfix.
Users on exchange are relayed out through this.
Once in awhile someone has a typo in their domain name.
Postfix bounces it back to exchange with 450 defer
Dec 18 15:48:40 smtp postfix-internal/smtpd[21635]:
On 12/18/2009, D G Teed (donald.t...@gmail.com) wrote:
>
> The remaining matches for 450 from running postconf | grep 450 are few:
Postconf -n output?
The mail server for something.com has been changed to mail.somethingelse.com
It's working fine for regular mail through a client.
Scripts (Drupal) on something.com when sending email though are failing.
How do I modify main.cf for the postfix install at something.com to
forward all mail generate
I notice from time to time by checking my mail queue that messages get
stuck there because users send to an invalid or non existing domain.
My Postfix server attempts to hold the message in queue for later
delivery assuming the remote server could be experiencing issues right
his moment. My questio
We have an smtp outbound-only service on postfix.
Users on exchange are relayed out through this.
Once in awhile someone has a typo in their domain name.
Postfix bounces it back to exchange with 450 defer
Dec 18 15:48:40 smtp postfix-internal/smtpd[21635]: NOQUEUE: reject: RCPT
from labrador2.exa
On Fri, Dec 18, 2009 at 01:40:25PM +, Anthony Campbell wrote:
> > > I commented out the following lines in /usr/lib/postfix/post-install
> > > which seem to refer to Solaris:
> > >
> > ># Flag obsolete objects. XXX Solaris 2..9 does not have "test -e".
> > > if [ -n "$obsolete_flag" ]
>
On 18 Dec 2009, Wietse Venema wrote:
> Anthony Campbell:
> > On 18 Dec 2009, Wietse Venema wrote:
> > > Anthony Campbell:
> > > >
> > > > I am running postfix via the Debian package in Sid.
> > > >
> > > > I get the following message during installation or with postfix check:
> > > >
> > > > po
Dne 12.12.2009 v 15:03 prasanna napsal(a):
> i have installed postfix 2.6.5, it is working fine. I am using
> dovecot IMAP server, where i have limited user mailbox size to 5MB. Whenever
> user quota is exceeded, Postfix sends failure bounce template mail to the
> sender immediately in
On Fri, Dec 18, 2009 at 10:46:13AM -0500, Wietse Venema wrote:
> > As there is no exit code to tell postfix that delivery failed due to
> > [..] is there any other way to [..] tell postfix to return a 5.2.2 DSN?
>
> [..] sending something to stdout that begins with a 5.2.2 status code.
Thanks. Th
Dne 18.12.2009 v 10:46 Wietse Venema napsal(a):
> > As there is no exit code to tell postfix that delivery failed due to
> > quota issues, is there any other way to insert a hook which checks and
> > rejects on a per-user basis after we know the size of the message, and
> > can tell postfix to ret
Noah Sheppard:
> On Thu, Dec 17, 2009 at 05:53:13PM -0500, Wietse Venema wrote:
> > Noah Sheppard:
> > > [..] postfix keeps trying to deliver the message for a long time
> >
> > procmail returns a TEMPORARY error condition to Postfix.
> > Don't blame Postfix for procmail brain damage.
> >
>
> Und
On Thu, Dec 17, 2009 at 05:53:13PM -0500, Wietse Venema wrote:
> Noah Sheppard:
> > [..] postfix keeps trying to deliver the message for a long time
>
> procmail returns a TEMPORARY error condition to Postfix.
> Don't blame Postfix for procmail brain damage.
>
Understood. Actually, this was our f
Anthony Campbell:
> On 18 Dec 2009, Wietse Venema wrote:
> > Anthony Campbell:
> > >
> > > I am running postfix via the Debian package in Sid.
> > >
> > > I get the following message during installation or with postfix check:
> > >
> > > postfix/usr/lib/postfix/post-install: line 493: test: too
On 18 Dec 2009, Wietse Venema wrote:
> Anthony Campbell:
> >
> > I am running postfix via the Debian package in Sid.
> >
> > I get the following message during installation or with postfix check:
> >
> > postfix/usr/lib/postfix/post-install: line 493: test: too many arguments
> > /usr/lib/postf
Anthony Campbell:
>
> I am running postfix via the Debian package in Sid.
>
> I get the following message during installation or with postfix check:
>
> postfix/usr/lib/postfix/post-install: line 493: test: too many arguments
> /usr/lib/postfix/post-install: line 493: test: too many arguments
>
> -Original Message-
> From: owner-postfix-us...@postfix.org [mailto:owner-postfix-
>
> clamav-milter (with ClamAV 0.95.3) works fine.
>
> We use clamav-milter during pre-queue so that we can 5xx during SMTP
> and
> not deal with it past that point. No need to worry about whether
> we're
>
I am running postfix via the Debian package in Sid.
I get the following message during installation or with postfix check:
postfix/usr/lib/postfix/post-install: line 493: test: too many arguments
/usr/lib/postfix/post-install: line 493: test: too many arguments
/usr/lib/postfix/post-install: li
2009/12/17 /dev/rob0 :
> On Thu, Dec 17, 2009 at 09:51:13AM +, T D wrote:
>> But then the users complained that the mail wasn't being delivered to
>> their IMAP mailbox, and it was being forwarded to the blackberry /
>> vodafone address around ten times!
>
> Content filtering without proper re
mouss put forth on 12/17/2009 7:40 AM:
> No. maybe did you remove a firewall block? postfix does rdns check for
> all connections (unless you disable that) so you should see the warnings
> however you order your smtpd checks.
No firewall changes. I did recently switch my dns resolvers to the new
32 matches
Mail list logo
