Our business has many clients, each of which is assigned a number. Using that
number, we assign an email address to receive and store email communications
for that client. So, for example 12...@mydomain.com is received by a wildcard
alias and deposited into one email account for all aliases.
On Tue, Jul 19, 2016 at 11:54:29AM -0400, Warren H. Prince wrote:
> Our business has many clients, each of which is assigned a number.
> Using that number, we assign an email address to receive and store
> email communications for that client. So, for example
> 12...@mydomain.com is received b
I'm reasonably certain that this is my own mistake, but I need help
tracking down what I've done wrong.
I have postfix/amavisd (and other software components) in a mail relay
role, sitting between an Exchange server and the Internet. All email
coming in from the Internet and all email heading out
On 2016-07-19 22:46, Shawn Heisey wrote:
Can I get help with this problem here? If so, what information do I
need to include?
sure, where is postconf -n ? :=)
its simple with postfix to reject own domains in postfix port 25, and
reqire sasl auth on port 587 and port 465
it does not really
Thanks for the help. I have servers in Google Cloud. They block outgoing mail
on 25, 465, and 587.
https://cloud.google.com/compute/docs/tutorials/sending-mail/
I know it's possible to do this as I did it on another server awhile ago but
can't seem to get this one to work.
Mark
--
View this
On 2016-07-19 23:35, markus79 wrote:
I see port 25 in my mail log and when I run mailq:
(connect to ALT1.ASPMX.L.GOOGLE.com[2607:f8b0:400c:c08::1a]:25: Network
is
unreachable)
ping6 -c 3 ipv6.google.com
what results ?
I see port 25 in my mail log and when I run mailq:
(connect to ALT1.ASPMX.L.GOOGLE.com[2607:f8b0:400c:c08::1a]:25: Network is
unreachable)
--
View this message in context:
http://postfix.1071664.n5.nabble.com/Postfix-can-t-send-external-email-tp85073p85108.html
Sent from the Postfix Users ma
root@wcp-2:/etc/postfix# ping6 -c 3 ipv6.google.com
connect: Network is unreachable
On Tue, Jul 19, 2016 at 4:39 PM, Benny Pedersen-2 [via Postfix] <
ml-node+s1071664n85109...@n5.nabble.com> wrote:
> On 2016-07-19 23:35, markus79 wrote:
> > I see port 25 in my mail log and when I run mailq:
> >
On 7/19/2016 4:10 PM, markus79 wrote:
> Thanks for the help. I have servers in Google Cloud. They block outgoing mail
> on 25, 465, and 587.
>
> https://cloud.google.com/compute/docs/tutorials/sending-mail/
>
You'll need a relayhost that accepts your mail on a non-standard
port, and then relays
On 7/19/2016 3:46 PM, Shawn Heisey wrote:
>
> I *thought* I had everything set up so it would check SPF records on any
> message coming in from the Internet, but one of our executives received
> a spam email that had another of our executives as the "From" address.
Are you talking about the From:
Thanks, but I've set up a server in Google Cloud to use 5877 in the past
when 587 was blocked without having to use a relayhost. I just can't access
that server now :(
On Tue, Jul 19, 2016 at 5:02 PM, Noel Jones-2 [via Postfix] <
ml-node+s1071664n85111...@n5.nabble.com> wrote:
> On 7/19/2016 4:10
On 7/19/2016 5:10 PM, markus79 wrote:
> Thanks, but I've set up a server in Google Cloud to use 5877 in the past
> when 587 was blocked without having to use a relayhost. I just can't access
> that server now :(
Sorry, that's not how email works. No server will accept mail on a
non-standard port
On 2016-07-19 23:45, markus79 wrote:
root@wcp-2:/etc/postfix# ping6 -c 3 ipv6.google.com
connect: Network is unreachable
then its not a postfix problem, but badly firewall, eq slack autoconfig
?
sorry cant help more
13 matches
Mail list logo
