Rocco Scappatura:
12:31:06.808714 O client.1395 server.25: . 1931191:1932551(1360)
ack
358 win 65178 (DF)
Can you show the TCP handshake (SYN/SYN+ACK/ACK) with TCP options.
You are right, there is no TCP option. I will try to dump another SMTP
session. This time directly on mail
Hello all,
Hope you all are well.
I have found a problem with my 1+1/2 months old mail server here. Some
times I get an error as below during sending email to an account as
temporary lookup problem
~~~``
postfix/trivial-rewrite[13203]: fatal:
J. Bakshi wrote:
Hello all,
Hope you all are well.
I have found a problem with my 1+1/2 months old mail server here. Some
times I get an error as below during sending email to an account as
temporary lookup problem
~~~``
postfix/trivial-rewrite[13203]: fatal:
Why?
If I want to avoid that the spammer wouldn't receive a response like this:
but it was rejected by the recipient domain. We recommend contacting the other
email provider for further information about the cause of this error. The error
that the other server returned was: 554 554 5.7.1
On 11/4/2008, Lluis Ribes ([EMAIL PROTECTED]) wrote:
If I want to avoid that the spammer wouldn't receive a response like this:
but it was rejected by the recipient domain. We recommend contacting
the other email provider for further information about the cause of
this error. The error that
OK!
I'm going to configure REJECT,
Thanks a lot
Lluís
-Mensaje original-
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] En nombre de Charles Marcus
Enviado el: martes, 04 de noviembre de 2008 15:47
Para: postfix-users@postfix.org
Asunto: Re: Use discard in a check_recipient_access
On
Which tcpdump version is this? Where are the time stamps and the
packets with data (Len0)?
tcpdump show only initial packet data by default and -s0 show all
data. Is usefull when decode HEX (-xX) or ASCII (-A)
I repeat, there is no need to look at the data itself.
However, this
I had been googling but with no avail since I have no clue how to
query. I hope you can tell me with directive to use, I will do the
rest of the homework :)
what I want to make is some kind of rule that does the following:
If an email message arrives from [EMAIL PROTECTED] to
[EMAIL PROTECTED]
Lluis Ribes wrote:
Why?
because:
- mail loss is bad. The RFC recommends against it (search the RFC for
frivoulously). ask those of us who keep criticizing hotmail for such
behaviour.
- with a reject at RCPT time, you don't lose your bandwidth and time
reading the message (the connection
Francisco Neira wrote:
I had been googling but with no avail since I have no clue how to
query. I hope you can tell me with directive to use, I will do the
rest of the homework :)
what I want to make is some kind of rule that does the following:
If an email message arrives from [EMAIL
I think I have solved the mystery. But I can offer you only a
workaround, to turn off selective ACK support.
Here is one event in a tcpdump file that I received a few hours
ago (full context is below the signature):
10:49:57.930285 80.74.176.142.25 217.11.85.59.2528: . ack
1998901
Brian Evans - Postfix List wrote:
Francisco Neira wrote:
I had been googling but with no avail since I have no clue how to
query. I hope you can tell me with directive to use, I will do the
rest of the homework :)
what I want to make is some kind of rule that does the following:
If an email
Rocco Scappatura:
I think I have solved the mystery. But I can offer you only a
workaround, to turn off selective ACK support.
Here is one event in a tcpdump file that I received a few hours
ago (full context is below the signature):
10:49:57.930285 80.74.176.142.25
I think I have solved the mystery. But I can offer you only a
workaround, to turn off selective ACK support.
Here is one event in a tcpdump file that I received a few hours
ago (full context is below the signature):
10:49:57.930285 80.74.176.142.25 217.11.85.59.2528: .
Hi,
I am now using the policyd as shown below:
main.cf
# SPF
spfpolicy_time_limit = 3600
smtpd_recipient_restrictions = ...
check_policy_service unix: private / spfpolicy
...
master.cf
#SPF
spfpolicy unix - nn - - spawn
user = nobody argv = /usr/lib/postfix/policyd
now the message
On Tue, Nov 4, 2008 at 1:56 PM, Márcio Luciano Donada
[EMAIL PROTECTED] wrote:
Hi,
I am now using the policyd as shown below:
main.cf
# SPF
spfpolicy_time_limit = 3600
smtpd_recipient_restrictions = ...
check_policy_service unix: private / spfpolicy
...
master.cf
#SPF
spfpolicy unix
On Tue, 04 Nov 2008 14:56:10 -0200 Márcio Luciano Donada [EMAIL PROTECTED]
wrote:
Hi,
I am now using the policyd as shown below:
main.cf
# SPF
spfpolicy_time_limit = 3600
smtpd_recipient_restrictions = ...
check_policy_service unix: private / spfpolicy
...
master.cf
#SPF
spfpolicy unix - nn -
Wietse Venema wrote:
[EMAIL PROTECTED]:
Hi,
I followed instructions from:
http://prantran.blogspot.com/2007/01...untu-with.html
to use postfix to send mails trough gmail.com using sendmail.
My problem is when my bugzilla uses sendmail to send mails to
specified addresses.
From time to time
Rocco Scappatura:
I think I have solved the mystery. But I can offer you only a
workaround, to turn off selective ACK support.
Here is one event in a tcpdump file that I received a few hours
ago (full context is below the signature):
10:49:57.930285 80.74.176.142.25
Bailo, John:
I set up postfix with the dkim-milter.
It works great when I am logged into the linux server and send
mail with the mail command.
However, if I try to connect to postfix from a remote computer,
and send mail using a client such as outlook, the DKIM-Signature
is not being
Do you think this is a better solution than trying to set the Internal
Hosts parameter?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Wietse Venema
Sent: Tuesday, November 04, 2008 10:42 AM
To: Postfix users
Subject: Re: DKIM-Signature not being added
Hi All!
Currently, I use the forwards in /etc/aliases like this:
# cat /etc/aliases
forward1: user1 user2
forward2: user3
forward3: user1 user2 user3
I wanna know if I can limit the use of forward3, because I want to
only the user9 send e-mail to forward3.
All users can send e-mail to forward1
Hi,
Could I use the DISCARD word in a check_recipient_access hash: rule? By
example:
%more /etc/postfix/access
[EMAIL PROTECTED] permit_mynetworks,DISCARD
or should I use use REJECT word. I dont want to send error reply if someone
sends mail to [EMAIL PROTECTED] from out of my
M. Rodrigo Monteiro пишет:
Hi All!
Currently, I use the forwards in /etc/aliases like this:
# cat /etc/aliases
forward1: user1 user2
forward2: user3
forward3: user1 user2 user3
I wanna know if I can limit the use of forward3, because I want to
only the user9 send e-mail to forward3.
All users
Thought most people here would get a kick out of this :)
Evan
http://news.bbc.co.uk/2/hi/uk_news/wales/7702913.stm
When officials asked for the Welsh translation of a road sign, they
thought the reply was what they needed.
Unfortunately, the e-mail response to Swansea council said in
mouss wrote:
J. Bakshi wrote:
Hello all,
Hope you all are well.
I have found a problem with my 1+1/2 months old mail server here. Some
times I get an error as below during sending email to an account as
temporary lookup problem
~~~``
postfix/trivial-rewrite[13203]: fatal:
Lluis Ribes wrote:
Hi,
Could I use the “DISCARD” word in a check_recipient_access hash: rule? By
example:
%more /etc/postfix/access
[EMAIL PROTECTED] permit_mynetworks,DISCARD
or should I use use REJECT word. I don’t want to send error reply if someone
sends mail to [EMAIL
J. Bakshi wrote:
Hello mouss,
hope you are well, thanks for your kind response.
shall I use proxy in all the maps option. I like to be confirmed as it
is a production server.
The settings for virtual user and domains where you suggestion fits is
#
##
?li?s Tam?s:
Udv / Greetings!
I did not have sysctl compiled in the kernel. that one caused the
problem. (the old .config become incmpatible with the new one and I
havent chacked is all options are in place)
I don't know what the affect of sysctl to postfix, but definately has.
The effect
Reinaldo de Carvalho:
Which tcpdump version is this? Where are the time stamps and the
packets with data (Len0)?
tcpdump show only initial packet data by default and -s0 show all
data. Is usefull when decode HEX (-xX) or ASCII (-A)
I repeat, there is no need to look at the data itself.
Rocco Scappatura:
Rocco Scappatura:
12:31:06.808714 O client.1395 server.25: . 1931191:1932551(1360)
ack
358 win 65178 (DF)
Can you show the TCP handshake (SYN/SYN+ACK/ACK) with TCP options.
You are right, there is no TCP option. I will try to dump another SMTP
session.
Rocco Scappatura:
I think I have solved the mystery. But I can offer you only a
workaround, to turn off selective ACK support.
Here is one event in a tcpdump file that I received a few hours
ago (full context is below the signature):
10:49:57.930285
Wietse Venema:
I don't know if this is a problem with Windows TCP/IP, or if this
is a problem with a firewall on the client side. Reportedly, some
firewalls randomize TCP sequence numbers but don't update the
sequence numbers in SACK fields. That would be a sure way to mess
up TCP.
Quoting
Wietse Venema wrote:
Wietse Venema:
I don't know if this is a problem with Windows TCP/IP, or if this
is a problem with a firewall on the client side. Reportedly, some
firewalls randomize TCP sequence numbers but don't update the
sequence numbers in SACK fields. That would be a sure way
The above two are very good suggestions.
In addition, thinking of doing this at client side.
You may setup a mail matching and forwarding rules in .procmailrc at
user's home to achieve this specific forwarding issues for each users.
You can avoid to touch server side config each time when this
Hi folks,
Debian Etch
Postfix
Cyrus
I stuck on unable to send mails couple days. Telnet localhost 25
fails to work with following warning on;
$ tail /var/log/mail.log
Nov 5 03:49:17 xen03 postfix/postfix-script[1239]: refreshing the
Postfix mail system
Nov 5 03:49:17 xen03
Stephen Liu [EMAIL PROTECTED] wrote:
Nov 5 03:49:45 xen03 postfix/smtpd[1245]: warning: unsupported SASL
server implementation: cyrus
Nov 5 03:49:45 xen03 postfix/smtpd[1245]: fatal: SASL per-process
initialization failed
# grep pwcheck /usr/local/lib/sasl2/smtpd.conf
#pwcheck_method:
--- Sahil Tandon [EMAIL PROTECTED] wrote:
Stephen Liu [EMAIL PROTECTED] wrote:
Nov 5 03:49:45 xen03 postfix/smtpd[1245]: warning: unsupported
SASL
server implementation: cyrus
Nov 5 03:49:45 xen03 postfix/smtpd[1245]: fatal: SASL per-process
initialization failed
# grep
On Wednesday, November 05, 2008 at 06:25 CET,
Stephen Liu [EMAIL PROTECTED] wrote:
[...]
I have tried building Postfix Virtual by following other 3 howtos
before, all packages download on Debian repo. After finish all servers
can't work properly. This is my 4th round.
I think I have
* Stephen Liu [EMAIL PROTECTED] wrote:
I'm following this howto;
POSTFIX
http://www.postfixvirtual.net/postfixvirtual.html#postfix
CYRUS_SASL
http://www.postfixvirtual.net/postfixvirtual.html#cyrussasl
building the mail server. All packages were compiled from sources.
Version;
40 matches
Mail list logo