I seem to have fixed this.
It appears that DNS WAS the cause. Resolution was not happening to me when
doing requests, but when Postfix was attempting to make the same request, it
appears to have failed from time to time.
I saw this in the logs:
May 21 15:28:53 mail postfix/scache[13448]:
Thanks for all the replies.
Yes, DNS is working as expected. I can resolve the relay host's address no
problem.
There is a firewall between them. Traffic is open between both sides. My
postfix server is running on 25587/tcp and the relay hosts are both
listening on the same. I can successfully
Hi there,
I've set up a mail server that should be relaying messages to a different
cluster of Postfix boxes. When I attempt to send a message to the first box,
mail sits in the active queue for 5 minutes before being (successfully)
relayed to the cluster of Postfix boxes. which is then delivered
Good morning Wietse,
I found that this was user error and simply adding username/ in my vmaps
file worked like a charm.
Additionally, I had to make sure Dovecot could access my mailboxes by
explicitly setting my UID/GID to vmail/vmail in
/etc/dovecot/conf.d/10-mail.conf
Thank you for your
Hi Postfix Users,
I am having some difficulty getting my mail to send where I'd like.
Our Postfix server supports a web application where the web app logs into
Postfix with a username and password (where the username is actually a
username - not username@domain).
This has caused some issues on
Wietse,
Thank you for your swift reply.
I am happy with where the mail is ending up as defined in
virtual_mailbox_base.
As for vmaps, I have the following (for the example I used in the above
e-mail):
t...@domain1.comdomain1.com/test/
Which I do understand should make all new e-mails
Every time I edit the vmaps file, I always run postmap /etc/postfix/vmaps.
I have reloaded postfix as requested and sent a local mail to
t...@domain1.com and my e-mail just bounces when the vmaps file is
structured as stated previously.
In my first post, what I posted was the output of postconf
Hi Sahil,
Sorry for my delayed response. I work in DEVOPS and we have had a crazy
release schedule!
I ran postfix set-permissions as root and did not see anything following -
just sent me to the next line.
I was working with another group within our company that uses Postfix just
for relay
Hi Wietse,
Apologies - I have VERY little Linux experience - all learned using Google
trying to get this mail server spun up. I've figured out the hard way that a
lot of my problems on getting this thing set up were permission related in
some form..
I have ran the command you requested. Here is
I just figured this out myself when the command failed.
My $setgid_group is set to postdrop and $queue_directory set to
/var/spool/postfix.
I have ran ls -ld for those directories you specified --
[root~]# ls -ld /var/spool/postfix/maildrop/
drwx-wx---. 2 postfix postdrop 4096 Mar 18 10:57
Hi Sahil,
Thank you for the suggestion. I have ran postfix set-permissions, but it
looks like the postdrop warning is still occurring on each message.
Thanks,
Joey
--
View this message in context:
http://postfix.1071664.n5.nabble.com/20-40-second-delays-Is-this-normal-tp65951p65964.html
Hello,
I have recently spun up a Postfix server that is currently in a testing
phase. It is currently not being used at the moment - so there is zero load
on this server.
I am actively using Postfix 2.11, SpamAssassin 3.3.1 and Dovecot 2.0.9 for
POP3.
When I try sending a basic test e-mail
Hi there,
I am currently in the testing phase of replacing Gordano with a Postfix
solution. First time RHEL user - so this has proven quite a challenge for
me!
This server is being spun up as a mail server for an enterprise application.
I believe I have gotten everything working, but would
Thanks for the quick reply!
Correct. This file does exist in /etc/postfix. The contents are that of the
same in the previous forum post I linked.
/name=/ REJECT no attachments allowed
--
View this message in context:
Well! This is quite embarrassing - and a great catch!
My main.cf had mime_header_check, while the file name was labeled
mime_header_checks!
Thanks so much! I do have one other issue that I will post in another topic.
:)
--
View this message in context:
15 matches
Mail list logo