Viktor Dukhovni via Postfix-users wrote in
:
|On Mon, Aug 26, 2024 at 04:59:47PM +, Ren Jyan via Postfix-users wrote:
|> I still want to try using a SOCKS5 proxy.
|
|I can try, but I personally prefer to not provide the kind of help which
|I balance I consider to be harming the real inter
On Mon, Aug 26, 2024 at 04:59:47PM +, Ren Jyan via Postfix-users wrote:
> I still want to try using a SOCKS5 proxy.
I can try, but I personally prefer to not provide the kind of help which
I balance I consider to be harming the real interests of the person
seeking help. A socks proxy for mai
ix.org
Cc: postfix-us...@dukhovni.org
Subject: [pfx] Re: ת��: Sending mail through vpn on postfix
It appears that Viktor Dukhovni via Postfix-users
said:
>> I'm deploying postfix on my vps, but my ISP has blocked outbound
>> traffic on port 25. ...
>You're unlikely to
On Sun, Aug 25, 2024 at 06:09:23PM +, Jyan Ren via Postfix-users wrote:
> I'm deploying postfix on my vps, but my ISP has blocked outbound
> traffic on port 25. To bypass this restriction, I am considering using
> a VPN based on the socks5 protocol to forward my SMTP traffic. I would
> like to
Just change a VPS.
Or, in my case, azure does block outgoing traffic to smtp port 25, but
they don’t block external port 587/465.
So I configured my postfix on azure to route message out via the
submission port of another VPS.
Regards
On 2024-08-26 02:09, Jyan Ren via Postfix-users wrote:
De
Jyan Ren via Postfix-users skrev den 2024-08-25 20:09:
I'm deploying postfix on my vps, but my ISP has blocked outbound
traffic on port 25.
install roundcube on vps, enjoy your isp blocking port 25
dont use soks5 ever
vpn is fine for roundcube
more help ?, show logs from postfix server if a
Dear Postfix Support Team,
Sorry to interrupt, but I hope this email finds you well.
I'm deploying postfix on my vps, but my ISP has blocked outbound traffic on
port 25. To bypass this restriction, I am considering using a VPN based on the
socks5 protocol to forward my SMTP traffic. I would like
5 in this instance? Port 25 will not work, but port 587
could work
however I do not see postfix trying that port. Sending mail from a
gmail accounts appears successful and my guess is because it does try
to use
port 587 when connecting to the destination mail server.
It is considered a best prac
Thanks everyone for your insights!
@Bernardo: I wasn´t aware that a delayed greeting could happen in the order of
20 seconds or so.
That did the trick!
@Wietse: Thank you as well for showing me how the transport maps work!
Case closed.
Regards,
Sebastiaan
On Saturday, July 23, 2022 18:36 C
On Sat, 23 Jul 2022, Sebastiaan la Fleur wrote:
Hello everyone!
Currently I am running into an issue that a (misconfigured) destination
mailserver does not accept mail on port 25. It allows a TCP connection but it
will not send a greeting. Instead, it expects mail to be send to port 587
whi
This requires Postfix version 3.
/etc/postfix/main.cf:
transport_maps = hash:/etc/postfix/transport
/etc/postfix/transport:
example.com smtp:example.com:123,example.com:234
NOT: smtp:example.com:123, smtp:example.com:234.
Run postmap hash:/etc/postfix/transport after editing the file.
I
however I do not see postfix trying that port. Sending mail from a gmail
accounts appears successful and my guess is because it does try to use
port 587 when connecting to the destination mail server.
TLS level is on 'may': smtp_tls_security_level = may
Thank you in advance for an
On Fri, Feb 12, 2021 at 11:33:53AM -0500, Wietse Venema wrote:
> Chris Green:
> > Just a quickie, how do I configure /etc/hostname etc. for a system at
> > isbd.uk?
> >
> > It really *is* just isbd.uk:-
> >
> > chris$ host isbd.uk
> > isbd.uk has address 92.243.2.29
> > isbd.uk mail i
Chris Green:
> Just a quickie, how do I configure /etc/hostname etc. for a system at
> isbd.uk?
>
> It really *is* just isbd.uk:-
>
> chris$ host isbd.uk
> isbd.uk has address 92.243.2.29
> isbd.uk mail is handled by 0 mail.vhdns.net.
>
> So, if I set /etc/hostname to isbd.uk then po
sending mail from host isbd.uk?
Just a quickie, how do I configure /etc/hostname etc. for a system at
isbd.uk?
It really *is* just isbd.uk:-
chris$ host isbd.uk
isbd.uk has address 92.243.2.29
isbd.uk mail is handled by 0 mail.vhdns.net.
So, if I set /etc/hostname to isbd.uk then postfix
Just a quickie, how do I configure /etc/hostname etc. for a system at
isbd.uk?
It really *is* just isbd.uk:-
chris$ host isbd.uk
isbd.uk has address 92.243.2.29
isbd.uk mail is handled by 0 mail.vhdns.net.
So, if I set /etc/hostname to isbd.uk then postfix thinks the domain
name is j
ipconfig:
> is, for example, from a user acct on the postfix server to an acct on the
> domain, postfix sends it to the proper edge transport server
Should Postfix send this recipient to this edge server? If it should,
then the error is not with Postfix.
> and then that
> server reports the error
I actually did google it, and since they all basically say "configure a send
connector" I came here, since I am dealing with both postfix and exchange
and have a working send connector configured.
I guess I should have explained it better, but the traffic I'm talking about
is, for example, from a
ipconfig:
> Hi all,
>
> I know this isn't a microsoft exchange forum, but I was hoping maybe someone
> could help me eliminate any potential configuration problems with postfix
> IRT the error I'm seeing on my exchange transport server.
>
> Disclaimer: I'm a complete noob with postfix. And pretty
Hi all,
I know this isn't a microsoft exchange forum, but I was hoping maybe someone
could help me eliminate any potential configuration problems with postfix
IRT the error I'm seeing on my exchange transport server.
Disclaimer: I'm a complete noob with postfix. And pretty noobish at
Exchange.
O
> On Nov 13, 2019, at 6:58 AM, Wietse Venema wrote:
>
> Implementations of the IDENT protocol (RFC 931) have been around
> for decennia.
Sure, but here's a comment from the source code of Debian's "pidentd":
* We have observed Debian identd (on a fairly busy dual-CPU machine)
* sometimes repo
Viktor Dukhovni:
> On Wed, Nov 13, 2019 at 03:14:36AM +0100, J?n Lalinsk? wrote:
>
> > Thanks for the insights. However, I am optimistic that for smtp sessions
> > this can be made to (mostly) work, because the check for UID of the
> > process holding the client port can be done some time after SM
On Wed, Nov 13, 2019 at 03:14:36AM +0100, Ján Lalinský wrote:
> Thanks for the insights. However, I am optimistic that for smtp sessions
> this can be made to (mostly) work, because the check for UID of the
> process holding the client port can be done some time after SMTP
> commands have been rec
Thanks for the insights. However, I am optimistic that for smtp sessions
this can be made to (mostly) work, because the check for UID of the
process holding the client port can be done some time after SMTP
commands have been received by Postfix, at which point the connection is
already established.
On Tue, Nov 12, 2019 at 05:13:05PM -0500, Viktor Dukhovni wrote:
> > To achieve this, I'd like to set up Postfix+Linux -based outgoing mail
> > server, possibly with some helper daemon. Any incoming TCP connection on
> > localhost:25 where Postfix listens will be handled in a way dependent on
> >
Dnia 12.11.2019 o godz. 21:56:51 Ján Lalinský pisze:
> To achieve this, I'd like to set up Postfix+Linux -based outgoing mail
> server, possibly with some helper daemon. Any incoming TCP connection on
> localhost:25 where Postfix listens will be handled in a way dependent on
> the UID of the proces
> On Nov 12, 2019, at 3:56 PM, Ján Lalinský wrote:
>
> To achieve this, I'd like to set up Postfix+Linux -based outgoing mail
> server, possibly with some helper daemon. Any incoming TCP connection on
> localhost:25 where Postfix listens will be handled in a way dependent on the
> UID of the p
Dear Postfix users,
I'm trying to set up email sending from local users on a shared
webhosting server. There are hundreds of different domains, each having
unique UNIX UID and they need smtp service directly available on
localhost:25, without any credentials checking. At the same time, I need
the
On 2019-09-29, Jaroslaw Rafa wrote:
> The only thing I can't do is I cannot completely avoid
> forwarding mail to Gmail accounts, because there are some addresses on my
> server that need to be kept as forwarding addresses after people moved to
> Gmail; but as I see from serve
this could be ineffective if it turns out that it is
> my domain name, and not my IP address, what Google "doesn't like".
Most email sender reputation is by IP.
> Even if
> this succeeds, there is no guarantee that in the future Google will not go
> crazy again and start tre
t;doesn't like". Even if
this succeeds, there is no guarantee that in the future Google will not go
crazy again and start treating my email as spam.
No, thanks. Trying to configure sending mail via Gmail's server looks like a
much more reasonable alternative compared to this...
--
Re
On Sun, Sep 29, 2019 at 05:33:53PM -0400, Viktor Dukhovni wrote:
> Reliably detecting a Google-operated SMTP server may be non-trivial.
That said, the Google SMTP server certificate does provide a crib
for the popular names (resorted):
posttls-finger: alt1.gmr-smtp-in.l.google.com[2a00:1450:
On Sun, Sep 29, 2019 at 09:50:12PM +0200, Jaroslaw Rafa wrote:
> Is it possible to somehow use a script in place of the lookup table for
> transport_maps ? Thus I could write a script that checks the MX and returns
> the appropriate result.
http://www.postfix.org/socketmap_table.5.html
> > T
Dnia 29.09.2019 o godz. 13:30:38 Wietse Venema pisze:
>
> There are two places where Postfix can do MX lookups for a remote
> recipient:
>
> - In the SMTP client.
>
> - In the SMTP server (check_recipient_mx_access).
>
> You can use check_recipient_mx_access to return 'filter:gmail-submission'
Dnia 29.09.2019 o godz. 13:21:53 Viktor Dukhovni pisze:
>
> The trouble is that such accounts are generally restricted to a
> single envelope sender address, likely with a matching single "From"
> address.
You can define in Gmail account settings alternate sender addresses that
this account is al
Jaroslaw Rafa:
> Hello,
> as Gmail is often putting e-mails from me into recipients' Spam folder, and
> there seems to be no solution for this (I tried everything to no avail), I'm
> considering an idea of sending e-mail to Gmail users via Gmail server, with
> help of a Gmail account specially crea
On Sun, Sep 29, 2019 at 06:16:05PM +0200, Jaroslaw Rafa wrote:
> I'm considering an idea of sending e-mail to Gmail users via Gmail server,
> with
> help of a Gmail account specially created for that purpose. (If that doesn't
> help then - I guess - nothing helps :( ).
The trouble is that such a
Hello,
as Gmail is often putting e-mails from me into recipients' Spam folder, and
there seems to be no solution for this (I tried everything to no avail), I'm
considering an idea of sending e-mail to Gmail users via Gmail server, with
help of a Gmail account specially created for that purpose. (If
> On Dec 10, 2018, at 8:00 PM, Sean Son
> wrote:
>
> Thank you for the reply. Can the client be configured to trust more
> than one SSL cert?
most of clients support more than one certificate authority.
On Mon, Dec 10, 2018 at 9:40 PM Viktor Dukhovni
wrote:
You've told us nothing about the
On Mon, Dec 10, 2018 at 9:40 PM Viktor Dukhovni
wrote:
> > On Dec 10, 2018, at 8:00 PM, Sean Son
> wrote:
> >
> > Thank you for the reply. Can the client be configured to trust more
> than one SSL cert?
>
> You've told us nothing about the client, so it would be a miracle
> if someone on the li
> On Dec 10, 2018, at 8:00 PM, Sean Son
> wrote:
>
> Thank you for the reply. Can the client be configured to trust more than one
> SSL cert?
You've told us nothing about the client, so it would be a miracle
if someone on the list could give an answer to that question.
Is the client running
On Mon, Dec 10, 2018 at 6:57 PM Viktor Dukhovni
wrote:
> > On Dec 10, 2018, at 6:41 PM, Sean Son
> wrote:
> >
> > 330462 Dec 7 20:39:21 mailer postfix/smtpd[12242]: SSL3 alert
> read:fatal:unknown CA
> > 330463 Dec 7 20:39:21 mailer postfix/smtpd[12242]: SSL_accept:failed
> in SSLv3 read clie
> On Dec 10, 2018, at 6:41 PM, Sean Son
> wrote:
>
> 330462 Dec 7 20:39:21 mailer postfix/smtpd[12242]: SSL3 alert
> read:fatal:unknown CA
> 330463 Dec 7 20:39:21 mailer postfix/smtpd[12242]: SSL_accept:failed in
> SSLv3 read client key exchange A
> 330464 Dec 7 20:39:21 mailer postfix/sm
330467 Dec 7 20:39:21 mailer postfix/smtpd[12242]: disconnect from
unknown[X.X.X.75]
I have substituted our IP addresses with X's for security purposes. Any
suggestions on how to fix this issue? It's preventing us from sending mail
from the monitoring server to the SMTP Server. The ONL
On 2018-10-20 16:26:33 -0700, gaurav.parashar wrote:
> Hii,
> I had installed postfix in Ubuntu 16.04 and it was working seamlessly. Some
> time back I upgraded it to Ubuntu 18.04 and suddenly emails stop coming to
> my inbox. It gave me this error:
> postfix/postdrop[27466]: warning: mail_queue_en
On Tue, 23 Oct 2018, Dominic Raferd wrote:
On Tue, 23 Oct 2018 at 09:06, B. Reino wrote:
On Sat, 20 Oct 2018, Wietse Venema wrote:
gaurav.parashar:
Hii,
I had installed postfix in Ubuntu 16.04 and it was working seamlessly.
Some
time back I upgraded it to Ubuntu 18.04 and suddenly emails
On Tue, 23 Oct 2018 at 09:06, B. Reino wrote:
> On Sat, 20 Oct 2018, Wietse Venema wrote:
>
> > gaurav.parashar:
> >> Hii,
> >> I had installed postfix in Ubuntu 16.04 and it was working seamlessly.
> Some
> >> time back I upgraded it to Ubuntu 18.04 and suddenly emails stop coming
> to
> >> my i
On Sat, 20 Oct 2018, Wietse Venema wrote:
gaurav.parashar:
Hii,
I had installed postfix in Ubuntu 16.04 and it was working seamlessly. Some
time back I upgraded it to Ubuntu 18.04 and suddenly emails stop coming to
my inbox. It gave me this error:
postfix/postdrop[27466]: warning: mail_queue_en
gaurav.parashar:
I had installed postfix in Ubuntu 16.04 and it was working seamlessly. Some
time back I upgraded it to Ubuntu 18.04 and suddenly emails stop coming to
my inbox. It gave me this error:
postfix/postdrop[27466]: warning: mail_queue_enter: create file
maildrop/675261.27466: Permissio
gaurav.parashar:
I had installed postfix in Ubuntu 16.04 and it was working seamlessly. Some
time back I upgraded it to Ubuntu 18.04 and suddenly emails stop coming to
my inbox. It gave me this error:
postfix/postdrop[27466]: warning: mail_queue_enter: create file
maildrop/675261.27466: Permissio
On Saturday, October 20, 2018 08:52:23 PM Wietse Venema wrote:
> gaurav.parashar:
> > Hii,
> > I had installed postfix in Ubuntu 16.04 and it was working seamlessly.
> > Some
> > time back I upgraded it to Ubuntu 18.04 and suddenly emails stop coming to
> > my inbox. It gave me this error:
> > post
gaurav.parashar:
> Hii,
> I had installed postfix in Ubuntu 16.04 and it was working seamlessly. Some
> time back I upgraded it to Ubuntu 18.04 and suddenly emails stop coming to
> my inbox. It gave me this error:
> postfix/postdrop[27466]: warning: mail_queue_enter: create file
> maildrop/675261.2
Hii,
I had installed postfix in Ubuntu 16.04 and it was working seamlessly. Some
time back I upgraded it to Ubuntu 18.04 and suddenly emails stop coming to
my inbox. It gave me this error:
postfix/postdrop[27466]: warning: mail_queue_enter: create file
maildrop/675261.27466: Permission denied
I res
On Sun, Aug 13, 2017, at 21:13, Wietse Venema wrote:
[...]
> > Aug 13 14:37:55 u0 postfix/pickup[6727]: C630B180CB9: uid=1000
> > from=
> >
> > Aug 13 14:37:55 u0 postfix/cleanup[6746]: C630B180CB9:
> > message-id=<20170813183755.C630B180CB9@u1>
> >
> > Aug 13 14:37:55 u0 postfix/qmgr[6728]:
Harry Putnam:
> Logs from attempting to send a message like this:
>
> mailx -v -s "TEST 170813_140410 u0" hp...@fastmail.fm < ~/txtmsg.txt
You're using mailx -v, therefore Postfix will send you an email
message with a summary of the delivery. I'll get back to that later.
Fist the message submitt
Wouldn't you need something like no-ip so your router can be found?
Try to ping your router from a device not on your network such as from a cell
phone.
Original Message
From: hp...@fastmail.fm
Sent: August 13, 2017 11:54 AM
To: postfix-users@postfix.org
Subject: Sending mail from
HDW: HP wx8600 work station, 2x Xeon X5470, 3.33GHz
Running Openindiana/hipster HOST (Ilumos branch of solaris 11)
Running ubunto 17.04 inside Vbox vm on above host
postfix-3.14, Sasl 2.1.27~
Attempting to get postfix setup
My situtation is single user on home lan with no real domain name
T
Michael Segel:
> Hi,
>
> I am curious about being able to send email to both Dovecot for
> the end user?s mail box and then also on to a stream where one can
> do some analytics? Or chain the streams so that you can do analytics
> on both in-bound and out-bound and then deliver it?
>
> I know t
Hi,
I am curious about being able to send email to both Dovecot for the end user’s
mail box and then also on to a stream where one can do some analytics?
Or chain the streams so that you can do analytics on both in-bound and
out-bound and then deliver it?
I know that it can be done (theoret
On Dec 22, 2016, at 12:36 PM, Wietse Venema wrote: # Final command. Shell will remove the temp file and exit with # Sendmail's exit code. /usr/sbin/sendmail "$@"And do not forget the '--' inpipe ... argv=/path/to/script -f ${sender} -- ${recipient}And the missing "< $msg" in the final command: /u
> On Dec 22, 2016, at 12:36 PM, Wietse Venema wrote:
>
>> # Final command. Shell will remove the temp file and exit with
>> # Sendmail's exit code.
>> /usr/sbin/sendmail "$@"
>
> And do not forget the '--' in
> pipe ... argv=/path/to/script -f ${sender} -- ${recipient}
And the
Viktor Dukhovni:
>
> > On Dec 22, 2016, at 3:51 AM, St?phane MERLE
> > wrote:
> >
> > First, I save the message in the file descriptor 3
> >
> >msg=$(mktemp /tmp/msg.XX) || exit 75
> >cat > $msg || { rm $msg; exit 75; }
> >exec 3< $msg || { rm $msg; exit 75; }
> >rm $msg
>
> On Dec 22, 2016, at 3:51 AM, Stéphane MERLE
> wrote:
>
> First, I save the message in the file descriptor 3
>
>msg=$(mktemp /tmp/msg.XX) || exit 75
>cat > $msg || { rm $msg; exit 75; }
>exec 3< $msg || { rm $msg; exit 75; }
>rm $msg
>
> then I use it by rewinding it :
>
Hi Viktor,
I though I new a little of bash but in fact no ... you're a bash king !
if I understood it well :
first, I save the message in the file descriptor 3
msg=$(mktemp /tmp/msg.XX) || exit 75
cat > $msg || { rm $msg; exit 75; }
exec 3< $msg || { rm $msg; exit 75; }
rm $
On Wed, Dec 21, 2016 at 05:00:19PM +0100, Stéphane MERLE wrote:
> lemail=$(cat)
Instead of buffering the message into a shell variable, buffer it
into a temporary file (and set a "trap" command to delete the file).
You can then inspect the file content before sending the right
message.
It is po
Hi Wietse,
Le 21/12/2016 à 16:46, Wietse Venema a écrit :
St?phane MERLE:
at the top of my bash script I got :
lemail=$(cat)
Aaeeiigghh. Why not let the sendmail command read stdin.
see more explanations below
sendmail -i "$@" "$additional_recipient" < "$msg"
will it work without the "-f
St?phane MERLE:
> at the top of my bash script I got :
>
> lemail=$(cat)
Aaeeiigghh. Why not let the sendmail command read stdin.
> sendmail -i "$@" "$additional_recipient" < "$msg"
>
> will it work without the "-f" ?
If you invoke the script via
pipe ... argv=/path/to/script -f ${sender}
Hi Viktor,
Le 21/12/2016 à 15:02, Viktor Dukhovni a écrit :
On Wed, Dec 21, 2016 at 10:42:37AM +0100, Stéphane MERLE wrote:
when I send the mail content via sendmail :
sendmail -t $nouveau_destinataire <<< $lemail
This is wrong on many levels.
1. It revives *header* recipients, possibl
> On Dec 21, 2016, at 9:10 AM, Ansgar Wiechers wrote:
>
>>3. I has a mysterious "<<<", instead of "<".
>
> `... <<< $var` is bash 4 syntactic sugar for `echo $var | ...`.
An exceedingly bad way to handle message content, especially
sans quotes around "$var".
--
Viktor.
On Wed, Dec 21, 2016 at 10:42:37AM +0100, Stéphane MERLE wrote:
> when I send the mail content via sendmail :
>
> sendmail -t $nouveau_destinataire <<< $lemail
This is wrong on many levels.
1. It revives *header* recipients, possibly creating mail
loops and/or double deliveries. NEV
Hi,
I did manage to pipe my emails to a bash script which filter and push to
an api some emails, but I would like to "forward" some of them to an
email address.
when I send the mail content via sendmail :
sendmail -t $nouveau_destinataire <<< $lemail
or
sendmail $nouveau_destinataire <<< $
Thanks !
just perfect ...
Stéphane
Le 26/11/2016 à 16:13, Wietse Venema a écrit :
St?phane MERLE:
Hi,
Hi,
I found this and it looks just perfect for this !
http://serverfault.com/questions/322657/how-can-i-route-some-emails-to-a-script-in-postfix
one more question, if my script die and c
St?phane MERLE:
> Hi,
>
> Hi,
>
> I found this and it looks just perfect for this !
>
> http://serverfault.com/questions/322657/how-can-i-route-some-emails-to-a-script-in-postfix
>
> one more question, if my script die and cannot process the mail (too
> much cpu or ... script bug), the mail is
Hi,
Hi,
I found this and it looks just perfect for this !
http://serverfault.com/questions/322657/how-can-i-route-some-emails-to-a-script-in-postfix
one more question, if my script die and cannot process the mail (too
much cpu or ... script bug), the mail is lost or will go back in queue ?
H
Hi,
I got a 2 dedicated postfix/dovecot servers that deal with return to
replyto mails. For now, I got a bash script that "read and parse" each
files in /Maildir/new and if it match some criterias (most on
TO/FROM/SUBJECT) send it to another domain mailbox, from that new
domain, the mails are
On Fri, 7 Aug 2015 16:27:35 -0400 (EDT),
wie...@porcupine.org (Wietse Venema) wrote :
> I suspect that they are enforcing a DMARC policy that requires
> modifications to list managers so that they replace the From: header
> address with the sender address of the mailing list.
>
> Google for "dmarc
On Fri, 7 Aug 2015 17:59:06 +,
Viktor Dukhovni wrote :
> Don't confuse "smtp" with "smtpd".
Gah, this is embarrassing.
This was indeed my understanding and intention, and I somehow still
managed to push myself into this trap. Many eyes, etc.
Thanks a lot, this part now does work as I intende
Vincent Pelletier:
> Hello,
>
> I have a Mailman + postfix setup (old versions: mailman 2.1.11,
> postfix 2.5.5), and the mail server of one of subscribers' domain
> started rejecting mails when "From" header domain is its own domain
> (foo.com MX rejecting incoming @foo.com mails). This of course
On Fri, Aug 07, 2015 at 01:51:34PM +0200, Vincent Pelletier wrote:
> foo.com mangle_from:
>
> master.cf:
> mangle_from unix - - - - - smtpd
> -o header_checks=pcre:/etc/postfix/mangle_from.pcre
Don't confuse "smtp" with "smtpd".
$ postconf -Mf smtp/unix
smtp unix - -
On Fri, 07 Aug 2015 18:53:49 +0200,
"wilfried.es...@essignetz.de" wrote :
> That makes me wonder. Do they know the difference between "envelope-to"
> and "to"-field, or "envelope-from" and "from"-field? (This makes me
> remember to the beginning of my fechmail era - they do not use fetchmail
> or
Am 07.08.2015 um 18:24 schrieb Vincent Pelletier:
> On Fri, 07 Aug 2015 17:10:11 +0200,
> "wilfried.es...@essignetz.de" wrote :
>> maybe this, from postfix doc, will help you:
>>
>> http://www.postfix.org/ADDRESS_REWRITING_README.html#generic
>
> The problem with this is that it will rewrite "To:
On Fri, 07 Aug 2015 17:10:11 +0200,
"wilfried.es...@essignetz.de" wrote :
> maybe this, from postfix doc, will help you:
>
> http://www.postfix.org/ADDRESS_REWRITING_README.html#generic
The problem with this is that it will rewrite "To:" field too, so
sending to ...@foo.com pushes to their SMTP
Hi,
maybe this, from postfix doc, will help you:
http://www.postfix.org/ADDRESS_REWRITING_README.html#generic
Willi
Am 07.08.2015 um 13:51 schrieb Vincent Pelletier:
> Hello,
>
> I have a Mailman + postfix setup (old versions: mailman 2.1.11,
> postfix 2.5.5), and the mail server of one of
Hello,
I have a Mailman + postfix setup (old versions: mailman 2.1.11,
postfix 2.5.5), and the mail server of one of subscribers' domain
started rejecting mails when "From" header domain is its own domain
(foo.com MX rejecting incoming @foo.com mails). This of course happens
when a @foo.com member
On 26/11/14 15:03, Cristiano Deana wrote:
> On Wed, Nov 26, 2014 at 2:42 PM, Paolo De Michele
> wrote:
>
>> Anyone can help me please?
> Not enough details (log, domains, anything), but this
>
> Received: from [172.16.2.153]
> (dynamic-adsl-78-15-215-90.clienti.tiscali.it. [78.15.215.90])
>
> cou
On Wed, Nov 26, 2014 at 2:42 PM, Paolo De Michele
wrote:
> Anyone can help me please?
Not enough details (log, domains, anything), but this
Received: from [172.16.2.153]
(dynamic-adsl-78-15-215-90.clienti.tiscali.it. [78.15.215.90])
could be a good start point.
--
Cris, member of G.U.F.I
Paolo De Michele:
> Hi there,
>
> I configured a postfix version 2.11 on ubuntu 14.04 LTS x64
> When I send an email to gmail account and other (like hotmail.it) the
> emails end up in the spam box (the IP domain is not blacklisted)
> I would know why.
Set up an IPv4 DNS PTR record that resolves
Hi there,
I configured a postfix version 2.11 on ubuntu 14.04 LTS x64
When I send an email to gmail account and other (like hotmail.it) the
emails end up in the spam box (the IP domain is not blacklisted)
I would know why. A normal user can send an email only with starttls
authentication (I activa
Hi,
I have finally figured out the problem and it was nothing to do with Postfix.
The application on the local server had been misconfigured and was supplying an
incorrect value (undefined) to the BCC field which had been completely
overlooked in the logs.
Apologies for taking up your time o
Steve Hawes:
> Will try that and see what I get though what I do not understand
> is why it works fine for a remote client but not if the client is
> localhost. What would cause the difference?
There are many examples where Postfix can make a query for non-existent
information. Trying to avoid on
Will try that and see what I get though what I do not understand is why it
works fine for a remote client but not if the client is localhost. What would
cause the difference?
Thanks for your help so far.
Steve
On 30 Sep 2014, at 15:20, Wietse Venema wrote:
> There is no "undefined" in Postfi
There is no "undefined" in Postfix so you have a bug in your
database lookups.
Test the queries (as seen in logfile) by hand.
When a result does not exist, the database MUST return NOTFOUND
The database MUST NOT return an empty result.
The database MUST NOT return "undefined" or other crap.
That was really logged by postfix. This is the bit that is driving me mad as
the To address is there at the start of the trivial-rewrite process but by the
time it finishes all that is left is
Steve
On 30 Sep 2014, at 14:29, Wietse Venema wrote:
> What does mean? Is that something that you
What does mean? Is that something that you changed, or is that
really logged by Postfix?
Wietse
Hi,
I am relatively new to postfix but have worked with many mail systems over the
years and am quite familiar with various flavours of Unix/Linux. My problem is
as follows:
I have a Centos 6.5 system running Plesk V12 on which I have selected Postfix
as the mailing system - let’s call this Se
On Tue, Feb 25, 2014 at 11:30:36PM +0100, Roberto Giordani wrote:
> queue_run_delay = 150s
> minimal_backoff_time = 150s
> maximal_backoff_time = 300s
Reducing the maximal backoff time likely makes things worse, not
better.
--
Viktor.
Roberto Giordani:
> Thank you for reply Noel,
> I've found some interesting info about smtp_connection_cache_destinations
> and I've added the IP of my relay.
>
> But to improve the interval between delivery and avoid a large of
> deferred mail what else do you think should I change in my conf?
he server deliveries about 40.000 emails, but during
working hours I receive repeated random periods where the Postfix
smtp client doesn't open any socket to destination main SMTPD server
and the maillog file write
dsn=4.4.2, status=deferred (conversation with
smtp.xxx.it[xxx.xx.xxx.xxx] timed ou
le write
>
> dsn=4.4.2, status=deferred (conversation with
> smtp.xxx.it[xxx.xx.xxx.xxx] timed out while sending MAIL FROM)
>
> This behavior continues for about 5 minutes and on the next queue
> manager run, all emails will be accepted and delivered.
>
> At first time I thoug
Roberto Giordani:
> dsn=4.4.2, status=deferred (conversation with
> smtp.xxx.it[xxx.xx.xxx.xxx] timed out while sending MAIL FROM)
>
> This behavior continues for about 5 minutes and on the next queue
> manager run, all emails will be accepted and delivered.
>
> At fi
1 - 100 of 214 matches
Mail list logo
