On 10/31/2013 12:19 PM, John Allen wrote:
> Which is "better", to put the various restrictions with the
> appropriate smtpd__restriction stanzas, or to put them all into
> the smtpd_recipient_restrictions stanza. I am assuming that
> smtpd_delay_reject is yes.
There is no "better".
Putting ev
On 10/31/2013 12:19 PM, John Allen wrote:
> Which is "better", to put the various restrictions with the appropriate
> smtpd__restriction stanzas, or to put them all into the
> smtpd_recipient_restrictions stanza. I am assuming that
> smtpd_delay_reject is yes.
>
> I have always assumed that pu
On 10/30/2013 12:03 PM, Wietse Venema wrote:
> I have no first-hand experience with this, but I expect that a Milter
> could do the job. Milters can be written in C, Python, and other
> languages. They're plugins that see the message envelope and content
> as it arrives. At the end they can make s
Which is "better", to put the various restrictions with the appropriate
smtpd__restriction stanzas, or to put them all into the
smtpd_recipient_restrictions stanza. I am assuming that
smtpd_delay_reject is yes.
I have always assumed that putting them in one place had the advantage
of allo
Dennison Williams skrev den 2013-10-31 16:43:
Oct 31 15:23:38 hostname postfix/smtp[1847]: 1EB7C1199C8:
to=, relay=smtp.provider.net[280.90.215.86]:25,
delay=0.03, delays=0/0/0.02/0.01, dsn=5.7.1, status=bounced (host
smtp.provider.net[280.90.215.86] said: 554 5.7.1
: Recipient address rejected:
On 31/10/2013 18:00, Sergio Mira wrote:
> My point is: how to get feedback from [SMTP Server] to know if my
> message was really sent or not?
If the message cannot be delivered by the SMTP server, it will send a
bounce message to the sender. To easily detect those bounces the
standard technique i
Guys, are you good?
I have following scenario:
[HTTP Server]: process messages
[SMTP Server]: only send messages
[HTTP Server] === connect to ===>>> [SMTP Server] === sends message
===>>> [world]
Ok, this is going well.
My point is: how to get feedback from [SMTP Server] to know if my
mess
-- William Holt--- http://www.elementarray.comOn Oct 31, 2013 11:49 AM, Wietse Venema wrote: Dennison Williams:
> I have what I think should be a simple setup that does not seem to be
> using the /etc/aliases file.
As documented /etc/aliases is used by the local(8) delivery agent, which
normally
-- William Holt--- http://www.elementarray.comOn Oct 31, 2013 11:49 AM, Wietse Venema wrote: Dennison Williams:
> I have what I think should be a simple setup that does not seem to be
> using the /etc/aliases file.
As documented /etc/aliases is used by the local(8) delivery agent, which
normally
-- William Holt--- http://www.elementarray.comOn Oct 31, 2013 11:49 AM, Wietse Venema wrote: Dennison Williams:
> I have what I think should be a simple setup that does not seem to be
> using the /etc/aliases file.
As documented /etc/aliases is used by the local(8) delivery agent, which
normally
Dennison Williams:
> I have what I think should be a simple setup that does not seem to be
> using the /etc/aliases file.
As documented /etc/aliases is used by the local(8) delivery agent, which
normally handles mail for domains in mydestination.
> # /etc/postfix/main.cf
> ...
> mydestination =
I have what I think should be a simple setup that does not seem to be
using the /etc/aliases file. I expect all mail sent to root to go to
sy...@domain.tld but it is going to r...@domain.tld. Can anyone point me
in the right direction to getting this working? Thanks in advance!
# /etc/postfix/ma
Thanks... the issue was, in fact, in resolv.conf.
On Wed, Oct 30, 2013 at 9:31 AM, Wietse Venema wrote:
> Roman Gelfand:
>> Looking at the tcp stream, below, of a smtp conversation, it appears
>> there is 5 second delay before the actual smtp conversation begins.
>> Is this normal behavior. If n
13 matches
Mail list logo