I have a workign mx server (virtual) which I cloned to create a second
mx server. I changed the hostname and /etc/hosts and any reference I
could find to the old "mx4" name to "mx2". I also made sure reverse dns
and dns is OK. However, when I send mail, the recipient mail server
reports the bel
On 1/19/2011 4:24 PM, Jeroen Geilman wrote:
What "variable" ? Unless it is defined in the same main.cf file, or
introduced by Debian's infamous /etc/mailname hack, this is invalid.
Unless myhostname is explicitly defined, postfix uses the FQDN
returned by gethostname(2).
What I meant is that I
We have an issue with our SmarterMail mailboxes, especially via IMAP
connections, where messages will become corrupted and/or deleted from
the server. Just curious if there was anyone else out there also using
Postfix and Smartermail together who has experienced the same sort of
issues, or if y
Locking methods should overlap with those used by all programs
otherwise files will be corrupted.
Wietse
Thanks, Wietse. I don't think postfix is corrupting any of the files.
They are relayed via a transport map to the SMTP server of SmarterMail
and then delivered to the users mailbox
Is there any postfix configuration that will allow rejected mail to be
viewed or mail from a certain user to be saved despite reject/accept
status for debugging? Postfix is blocking an incoming message saying
mx1 postfix/cleanup[7139]: 6F3FBE4079: reject: header From: "ts2"
from mta319.sina.
On 3/5/2012 1:22 PM, Brian Evans - Postfix List wrote:
Read the message more closely: 'reject: header From: "ts2"'
Thanks, I was thinking these two things were separate statements but yes
of course the From address is of a different syntax and appears later in
the output.
Do you have a header
On 3/5/2012 2:39 PM, /dev/rob0 wrote:
You might do better if you told us what you're trying to do. What
problem are you trying to solve with this?
These checks are rather legacy -- I think probably a general set of
rules from someones posting here once upon a time. This particular check
was blo
> You enabled some "deep protocol" tests as documented:
> http://www.postfix.org/POSTSCREEN_README.html#after_220
OK, I wondered if this was part of it because I did see that it couldn't
pass the connection over to smtpd and would require the other host to try
again. I guess I wasn't expecting t
>
> you see in your log usually the same as the client get as answer what is
> helpful if someone is complaining to you about getting message XYZ
>
> you see in your log usually the same as the client get as answer what
> is helpful if someone is complaining to you about getting message XYZ
I
>
> yes, but you are missing that this message is the answer of postgrey which
is
> only redirected via postfix to the client, from the view of SMTP it is 450
That's OK -- postgrey is supplying me with useful information which quickly
leads me to the answer to my question: why is this message 450
Could someone help me figure out which rule exactly is blocking this e-mail?
We are trying to migrate a domain to another e-mail service and in the
meantime the new service is sending mail from a domain that postfix accepts
mail for. Whenever that migrating domain sends mail to a domain hosted on
t
>
> and another
>
> > check_recipient_access
> > pcre:/etc/postfix/MISC_CHECKS/ascii.pcre, check_sender_mx_access
> > cidr:/etc/postfix/NETWORK_CHECKS/drop.cidr, check_policy_service
> > inet:127.0.0.1:10023, check_helo_access
> > pcre:/etc/postfix/NETWORK_CHECKS/helo_hostnames.pcre,
> > pcre:/et
2012 at 11:14:43AM -0500, James Chase wrote:
> [attribution reconstructed]
> > > > James:
> > > rob0:
> > > and another
> > >
> > > > check_recipient_access
> > > > pcre:/etc/postfix/MISC_CHECKS/ascii.pcre, check_sender_mx_access
>
13 matches
Mail list logo
