On 31 Jul 2013, at 22:20 , LuKreme wrote:
> smtp unix - - - - - smtp
Well, yes, *that* was stupid.
smtp unix - - n - - smtp
*cough*
Thanks Noel, wouldn't have gotten there without you.
--
On a scale of one to ten, it sucked.
On 31 Jul 2013, at 21:52 , Noel Jones wrote:
> Looks as if you clobbered your smtp transport "smtp unix ... smtp"
>
>> smtp inet n - n - 1 postscreen
>> smtpd pass - - n - - smtpd
Am I suppose to have three lines?
adding
On 7/31/2013 8:31 PM, Andrew Ho wrote:
> I have a complicated settings, and I hope I can have some advice.
>
> I setup the access rule to block the outsider sending mails to the
> internal mail group.
>
> This is what I did.
>
> /etc/postfix/main.cf
>
> .
> che
On 7/31/2013 8:33 PM, LuKreme wrote:
>
> On 31 Jul 2013, at 17:35 , Wietse Venema wrote:
>
>>
>> http://www.postfix.org/DEBUG_README.html#logging
>
> Since I last stopped and started postfix (2.10.1):
>
> # egrep '(warning|error|fatal|panic):' /var/log/maillog
> Jul 31 18:47:59 mail postfix/qm
This is the behavior of Postfix: the mail will be returned to sender if the
destination can't be found but will be deferred if the destination can't be
reachable.
It's different between NOT FOUND and CAN'T BE REACHABLE. NOT FOUND means
send NDR to sender (situation you meet now), but CAN'T BE REAC
Actually, the program a) grabs pop3 object b) parses it c) modifies
subject slightly with certain keywords based on email contents d)
based on it builds smtp object. Hence, the from and to of the smtp
object is being assigned by from and to of the parsed pop object. So,
it is not a resend. The t
On Wed, Jul 31, 2013 at 09:31:20PM -0400, Roman Gelfand wrote:
> We are running an application which pulls mail from yahoo pop3 server
> and ultimately resends it, via local postfix server, keeping the same
> from and to addresses.
This is not generally possible. POP3 does not record the envelop
On 31 Jul 2013, at 17:35 , Wietse Venema wrote:
>
> http://www.postfix.org/DEBUG_README.html#logging
Since I last stopped and started postfix (2.10.1):
# egrep '(warning|error|fatal|panic):' /var/log/maillog
Jul 31 18:47:59 mail postfix/qmgr[81937]: warning: connect to transport
private/smtp
I have a complicated settings, and I hope I can have some advice.
I setup the access rule to block the outsider sending mails to the
internal mail group.
This is what I did.
/etc/postfix/main.cf
.
check_client_access hash:/etc/postfix/access
.
We are running an application which pulls mail from yahoo pop3 server
and ultimately resends it, via local postfix server, keeping the same
from and to addresses. The way I see it, there are rare instances
where from domain requires strict dkim enforcement. As a result,
yahoo rejects it notifyin
excellent.. thank you
On Wed, Jul 31, 2013 at 7:32 PM, Wietse Venema wrote:
> Roman Gelfand:
>> Is there a way to blacklist outbound email which was previously hard-bounced?
>>
>> For instance, if outgoing email comes back with codes 550 or 554, I
>> would like that on subsequent times it doesn't
Cerebus the Aardvark:
> I have a few accounts who forward a copy of all their mail to gmail
> addresses. For example, this account mirrors to a gmail account so I have
> access to my mailing list archives even when I am working on my server.
>
> While testing postfix 2.10 I am getting:
>
> Jul 31
Roman Gelfand:
> Is there a way to blacklist outbound email which was previously hard-bounced?
>
> For instance, if outgoing email comes back with codes 550 or 554, I
> would like that on subsequent times it doesn't leave the server.
Wietse:
> You want to block:
> - The same sender?
> - The same r
I have a few accounts who forward a copy of all their mail to gmail
addresses. For example, this account mirrors to a gmail account so I have
access to my mailing list archives even when I am working on my server.
While testing postfix 2.10 I am getting:
Jul 31 13:10:20 mail postfix/error[71592]:
The same recepient
On Wed, Jul 31, 2013 at 4:52 PM, Wietse Venema wrote:
> Roman Gelfand:
>> Is there a way to blacklist outbound email which was previously hard-bounced?
>>
>> For instance, if outgoing email comes back with codes 550 or 554, I
>> would like that on subsequent times it doesn't le
Roman Gelfand:
> Is there a way to blacklist outbound email which was previously hard-bounced?
>
> For instance, if outgoing email comes back with codes 550 or 554, I
> would like that on subsequent times it doesn't leave the server.
You want to block:
- The same sender?
- The same recipient?
- T
Is there a way to blacklist outbound email which was previously hard-bounced?
For instance, if outgoing email comes back with codes 550 or 554, I
would like that on subsequent times it doesn't leave the server.
Thanks in advance
LuKreme:
> When testing postfix2.10 against my master.cf and main.cf, it
> throws up a complaint about this line:
>
> procmail unix - n n - - pipe -o flags=uhFORD
> user=vpopmail argv=/usr/local/bin/procmail -t -m USER=${recipient}
> EXTENSION=${extension} /usr/lo
On 2013-07-31 2:53 PM, wie...@porcupine.org (Wietse Venema)
wrote:
Charles Marcus:
When you say 'the verifieD MUST disconnect...', I'm assuming you
meant 'verifieR' - meaning, their server, the one connecting to mine
sending VRFY probes?
Yes. Even when the verifier sends only known recipient
Drew Mazurek:
> Is there a configuration that will do what I want -- if a domain doesn't
> exist at all, Postfix will defer rather than bounce?
It's called soft_bounce=yes. Use with care: this will defer ALL
bounces including "user unknown" and other errors.
smtp_defer_if_no_mx_address_found is f
When testing postfix2.10 against my master.cf and main.cf, it throws up a
complaint about this line:
procmail unix - n n - - pipe -o flags=uhFORD
user=vpopmail argv=/usr/local/bin/procmail -t -m USER=${recipient}
EXTENSION=${extension} /usr/local/etc/procmailrc.c
Charles Marcus:
> On 2013-07-31 1:23 PM, wie...@porcupine.org (Wietse Venema)
> wrote:
> > That*is* a problem. Postfix will slow down and eventually hang
> > up when a client sends too many commands that cause an error
> > reply (as in VERY with a non-existent recipient).
> >
> > To make this ro
I have a question about smtp_defer_if_no_mx_address_found. Our cloud-based
app servers handle application-specific mail that's destined for them, and
these servers aren't static -- new ones are brought up and old ones are
shut down as needed. A special internal MX record (I'll call it
app-mx.host
On 2013-07-31 1:23 PM, wie...@porcupine.org (Wietse Venema)
wrote:
That*is* a problem. Postfix will slow down and eventually hang
up when a client sends too many commands that cause an error
reply (as in VERY with a non-existent recipient).
To make this robust the verified MUST disconnect afte
DTNX Postmaster:
> >> 2013-07-31T10:48:39-04:00 myhost postfix-25/smtpd[17729]: lost connection
> >> after VRFY from smtp446.redcondor.net[208.80.204.46]
Not a real problem...
> > with occasional
> >
> >> 2013-07-31T10:46:28-04:00 myhost postfix-25/smtpd[17993]: too many errors
> >> after VRFY
On Jul 31, 2013, at 18:19, Charles Marcus wrote:
> We are testing a new outsourced anti-spam service (Edgewave/RedCondor). We
> are letting their systems check for valid recipients using the VRFY command,
> but their default verifier uses , instead of
> as the FROM address when verifying. Bec
Hi all,
We are testing a new outsourced anti-spam service (Edgewave/RedCondor).
We are letting their systems check for valid recipients using the VRFY
command, but their default verifier uses ,
instead of as the FROM address when verifying.
Because I employ anti-spoofing (anything from/to on
James Day:
> Hello list,
>
> Hopefully a simple question but I can't seem to find the answer
> in the documentation (maybe my Google skills are lacking!).
>
> I'm using smtpd_sender_login_maps to ensure that users relaying
> only send mail from their own domains.
>
> Is it possible to allow an exc
Hello list,
Hopefully a simple question but I can't seem to find the answer in the
documentation (maybe my Google skills are lacking!).
I'm using smtpd_sender_login_maps to ensure that users relaying only send mail
from their own domains.
Is it possible to allow an exception for out of office
29 matches
Mail list logo
