Re: [Mailman-Users] Undelivered Mail Returned to Sender
John Levine writes: > In article <20180804141855.7510026c1...@sharky3.deepsoft.com> you write: > >-=-=-=-=-=- > > > >Do you have access to your inbound mail server? If so, you need to > >arrange for that server to *reject* all mail connections from > >qq.com. qq.com is a *notorious* source of spam (there are no > >legitimate E-Mail addresses @qq.com). You might also want to > >firewall Chinese IP addresses as well. > > Actually, there are millions of legitimate e-mail addrsses at qq.com. > It's Tencent, the giant Chinese company that owns Wechat, which has > 900 million active users, all with an e-mail address linked to their > Wechat accounts. > > Nearly all of the users are in China, so if you don't expect anyone > from China to subscribe to your lists, I suppose you can block them. Thanks John! Saved me the trouble. Also, if Postfix REJECT is what Mailman thinks of as "reject" (return to sender), it's preferable to (silently) DISCARD on the off chance that the address was spoofed or hijacked. Steve -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Undelivered Mail Returned to Sender
On 08/04/2018 06:25 AM, Jon Clements wrote: > Sorry, but can anyone tell me how to stop this from happening? I receive > one of these in Spam every minute. What is happening is spam is being sent from (in this case) <1975834...@qq.com> to . That is being forwarded from Mailman to the list owner and Google is rejecting the message and you are seeing the reject notice. Others have suggested configuring the MTA to not accept mail from qq.com. Another approach is to improve the spam filtering in general on the server so this mail doesn't get to Mailman. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Undelivered Mail Returned to Sender
In article <20180804141855.7510026c1...@sharky3.deepsoft.com> you write: >-=-=-=-=-=- > >Do you have access to your inbound mail server? If so, you need to arrange for >that server to *reject* all mail connections from qq.com. qq.com is a >*notorious* source of spam (there are no legitimate E-Mail addresses @qq.com). >You might also want to firewall Chinese IP addresses as well. Actually, there are millions of legitimate e-mail addrsses at qq.com. It's Tencent, the giant Chinese company that owns Wechat, which has 900 million active users, all with an e-mail address linked to their Wechat accounts. Nearly all of the users are in China, so if you don't expect anyone from China to subscribe to your lists, I suppose you can block them. -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] 'Undelivered Mail Returned to Sender' error when using an e-mail from a domain co-hosted with the one used for Mailman lists
Following on my last below post, I'd wish to report a small additional problem that I encountered after applying the '$alias_maps' fix to the 'local_recipient_maps' parameter. Whereas it effectively solved the 'Undelivered Mail Returned to Sender' issue when using a mail account from say virtual 'domain.net' co-hosted with say virtual 'domain.org' on the same physical VPS, it didn't resolve it when using a mail account from the same domain attributed to Mailman (as declared in the 'mm_cf.py' file)... To illustrate this, here is the related case set-up : - domain.net and domain.org are co-resident on the same host VPS12345, - domain.org is the one we use for mailman lists - link : http://lists.domain.org/mailman/listinfo, - we get no mail rejection when using the account na...@domain.net with a list created on 'lists.domain.org' (after the previous fix), - we get an 'Unknown User' mail rejection when using the na...@domain.org with a list created on 'lists.domain.org' (new problem observed). The kind of rejection error notification we then get is depicted thereafter : *** POST SUBMISSION TO TESTLIST *** From : Admin Lists DomainORG [mailto:admin-li...@domain.org] Sent : tuesday 29 april 2014 20:11 To : testl...@domain.org Subject : Some topic line... Some content to publication on the TestList list... *** UNDELIVERED MAIL NOTIFICATION RESPONSE *** From : MAILER-DAEMON (Mail Delivery System) [mailto:MAILER-DAEMON (Mail Delivery System)] Sent : tuesday 29 april 2014 20:11 To : admin-li...@domain.org Subject : Undelivered Mail Returned to Sender This is the mail system at host vps12345.ovh.net. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system testl...@domain.org : user unknown _ Is there another Postfix parameter which govern the behavior of local 'unix:passwd.byname' versus 'virtual-mailman' type email accounts defined on the SAME DOMAIN as the one specifically used for Mailman ? If it turns out that there is a restriction on such particular usage, we could live with it by not using same domain-based email addresses as the one devoted to Mailman. Many thanks for any hint regarding such reported behavior... - - - Jacques Setton jset...@waycast.com -Message d'origine- De : Jacques Setton [mailto:jset...@waycast.com] Envoyé : dimanche 27 avril 2014 21:05 À : 'Mark Sapiro' Cc : 'mailman-users@python.org' Objet : RE: [Mailman-Users] 'Undelivered Mail Returned to Sender' error when using an e-mail from a domain co-hosted with the one used for Mailman lists By default, local_recipient_maps includes $alias_maps, and I *think* it should in your case. Why this lack would cause Postfix to use the virtual_transport rather than local in just this one case is really a question for postfix-us...@postfix.org or some other Postfix resource, but you might try local_recipient_maps = unix:passwd.byname $alias_maps Very well spotted ! This is indeed the source of the mail rejection behavior that I have reported on when using a locally-hosted mail accounts on the same VPS which also hosts Mailman. The 'postconf -d' command output shows the following default setting : alias_maps = hash:/etc/aliases, nis:mail.aliases local_recipient_maps = proxy:unix:passwd.byname $alias_maps The 'postconf -n' command output shows the following (re)specified setting : alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases local_recipient_maps = unix:passwd.byname For some unclear reason, in the distribution we are using the '$allias_maps' parameter had been removed from the 'local_recipient_maps' setting in the Postfix 'main.cf' configuration file. After redefining the line as local_recipient_maps = unix:passwd.byname $alias_maps and doing a few test, it appears that we can now successfully use local mail accounts in relation with Mailman. or simply removing that line from main.cf and see if that helps. No need to do that as the above corrective action did fully resolve the problem. Many thanks, Mark, for your very effective guidance on this issue ! - - - Jacques Setton jset...@waycast.com -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive
Re: [Mailman-Users] 'Undelivered Mail Returned to Sender' error when using an e-mail from a domain co-hosted with the one used for Mailman lists
On 04/30/2014 04:08 AM, Jacques Setton wrote: To illustrate this, here is the related case set-up : - domain.net and domain.org are co-resident on the same host VPS12345, - domain.org is the one we use for mailman lists - link : http://lists.domain.org/mailman/listinfo, - we get no mail rejection when using the account na...@domain.net with a list created on 'lists.domain.org' (after the previous fix), - we get an 'Unknown User' mail rejection when using the na...@domain.org with a list created on 'lists.domain.org' (new problem observed). The kind of rejection error notification we then get is depicted thereafter : What you posted doesn't help. What is needed is the relevant Postfix log messages, but based on your prior issue, I'm sure that *this* massage is being relayed via the 'dovecot LDA rather than Postfix's 'local' LDA. Is there another Postfix parameter which govern the behavior of local 'unix:passwd.byname' versus 'virtual-mailman' type email accounts defined on the SAME DOMAIN as the one specifically used for Mailman ? So the issue appears to be that na...@domain.org is not a real address, but only a virtual one. I.e. mane2 is not in the unix passwd file. If it turns out that there is a restriction on such particular usage, we could live with it by not using same domain-based email addresses as the one devoted to Mailman. Do you know why your Postfix configuration has virtual_transport = dovecot If you don't need that, I think removing it will solve this, but it is likely required for dome other functionality having to do with your virtual_mailbox_domains. In any case, this is a Postfix issue. The only Mailman involvement is that for mail to a Mailman list from *some* addresses, the 'dovecot' relay is used rather than the 'local' You could try appending $virtual_mailbox_maps to local_recipient_maps, but that would probably have the same effect as removing virtual_transport = dovecot. Many thanks for any hint regarding such reported behavior... I'm sure there are people much more knowledgeable about Postfix than I, and those people probably are reachable through Postfix support resources. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] 'Undelivered Mail Returned to Sender' error when using an e-mail from a domain co-hosted with the one used for Mailman lists
By default, local_recipient_maps includes $alias_maps, and I *think* it should in your case. Why this lack would cause Postfix to use the virtual_transport rather than local in just this one case is really a question for postfix-us...@postfix.org or some other Postfix resource, but you might try local_recipient_maps = unix:passwd.byname $alias_maps Very well spotted ! This is indeed the source of the mail rejection behavior that I have reported on when using a locally-hosted mail accounts on the same VPS which also hosts Mailman. The 'postconf -d' command output shows the following default setting : alias_maps = hash:/etc/aliases, nis:mail.aliases local_recipient_maps = proxy:unix:passwd.byname $alias_maps The 'postconf -n' command output shows the following (re)specified setting : alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases local_recipient_maps = unix:passwd.byname For some unclear reason, in the distribution we are using the '$allias_maps' parameter had been removed from the 'local_recipient_maps' setting in the Postfix 'main.cf' configuration file. After redefining the line as local_recipient_maps = unix:passwd.byname $alias_maps and doing a few test, it appears that we can now successfully use local mail accounts in relation with Mailman. or simply removing that line from main.cf and see if that helps. No need to do that as the above corrective action did fully resolve the problem. Many thanks, Mark, for your very effective guidance on this issue ! - - - Jacques Setton jset...@waycast.com -Message d'origine- De : Mark Sapiro [mailto:m...@msapiro.net] Envoyé : vendredi 25 avril 2014 20:40 À : Jacques Setton Cc : mailman-users@python.org Objet : Re: [Mailman-Users] 'Undelivered Mail Returned to Sender' error when using an e-mail from a domain co-hosted with the one used for Mailman lists On 04/25/2014 03:25 AM, Jacques Setton wrote: 1) Selected Sequence from /var/log/maillog ... Apr 21 02:49:56 vps12345 postfix/smtp[9414]: F030911C008: to=mailman-requ...@domain.org, relay=127.0.0.1[127.0.0.1]:10024, delay=0.73, delays=0.26/0.01/0/0.46, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 9F72D11C00A) Apr 21 02:49:56 vps12345 postfix/smtpd[9419]: disconnect from localhost.localdomain[127.0.0.1] Apr 21 02:49:56 vps12345 dovecot: auth: sql(mailman-requ...@domain.org): Unknown user Apr 21 02:49:56 vps12345 postfix/pipe[9420]: 9F72D11C00A: to=mailman-requ...@domain.org, relay=dovecot, delay=0.04, delays=0.01/0.01/0/0.02, dsn=5.1.1, status=bounced (user unknown) Delivery to Mailman is via aliases. The dovecot LDA does not use your aliases. Delivery to Mailman must be via the local LDA. Something in your Postfix configuration is telling it to relay this particular mail via the dovecot transport rather than the local transport. That's why it bounces. The question is what's causing it. I suspect it has to do with two things in your Postfix configuration: local_recipient_maps = unix:passwd.byname and virtual_transport = dovecot By default, local_recipient_maps includes $alias_maps, and I *think* it should in your case. Why this lack would cause Postfix to use the virtual_transport rather than local in just this one case is really a question for postfix-us...@postfix.org or some other Postfix resource, but you might try local_recipient_maps = unix:passwd.byname $alias_maps or simply removing that line from main.cf and see if that helps. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] 'Undelivered Mail Returned to Sender' error when using an e-mail from a domain co-hosted with the one used for Mailman lists
Hello Mark,
Not until you do as I asked before and post the resulting output from
grepping the mail log for the Postfix queue id of a returned message.
Based on your prior post, this would be something like
grep 9F72D11C00A /var/log/maillog
Also it might help to see your transport maps - /etc/postfix/transport
Postfix 'transport' file content
Sorry, but I didn't immediately spot that you were asking for this type of
information which I am now enclosing below, as requested :
(Reminder : 'domain.org' and 'domain.net' are hosted on the same VPS and
'domain.org' is the virtual domain that has been specified in the
'mm_cfg.py' config file. The declared MTA is 'Postfix'.)
1) Selected Sequence from /var/log/maillog
___
Apr 21 02:49:55 vps12345 postfix/smtpd[9396]: F030911C008:
[details-removed*], sasl_method=PLAIN, sasl_username=j.set...@domain.net
Apr 21 02:49:56 vps12345 dovecot: pop3-login: Login:
user=j.set...@domain.net, method=PLAIN, rip=83.xxx.xxx.xxx*,
lip=37.yyy.yyy.yyy*, mpid=9413
Apr 21 02:49:56 vps12345 postfix/cleanup[9412]: F030911C008:
message-id=001901cf5cfb$994e5cb0$cbeb1610$@domain.net
Apr 21 02:49:56 vps12345 postfix/qmgr[9319]: F030911C008:
from=j.set...@domain.net, size=900, nrcpt=1 (queue active)
Apr 21 02:49:56 vps12345 dovecot: pop3(j.set...@domain.net): Disconnected:
Logged out top=0/0, retr=0/0, del=0/6, size=15209
Apr 21 02:49:56 vps12345 dovecot: pop3-login: Login:
user=admin-w...@domain.net, method=PLAIN, rip=83.xxx.xxx.xxx*,
lip=37.yyy.yyy.yyy*, mpid=9418
Apr 21 02:49:56 vps12345 dovecot: pop3(admin-w...@domain.net): Disconnected:
Logged out top=0/0, retr=0/0, del=0/3, size=21056
Apr 21 02:49:56 vps12345 postfix/smtpd[9419]: connect from
localhost.localdomain[127.0.0.1]
Apr 21 02:49:56 vps12345 postfix/smtpd[9419]: 9F72D11C00A:
client=localhost.localdomain[127.0.0.1]
Apr 21 02:49:56 vps12345 postfix/cleanup[9412]: 9F72D11C00A:
message-id=001901cf5cfb$994e5cb0$cbeb1610$@domain.net
Apr 21 02:49:56 vps12345 postfix/qmgr[9319]: 9F72D11C00A:
from=j.set...@domain.net, size=1364, nrcpt=1 (queue active)
Apr 21 02:49:56 vps12345 amavis[24558]: (24558-09) Passed CLEAN
{RelayedInbound}, [83.xxx.xxx.xxx*]:56370 [83.xxx.xxx.xxx*]
j.set...@domain.net - mailman-requ...@domain.org, Message-ID:
001901cf5cfb$994e5cb0$cbeb1610$@domain.net, mail_id: EMVkrlB1bIaY, Hits:
-0.999, size: 866, queued_as: 9F72D11C00A, 462 ms
Apr 21 02:49:56 vps12345 postfix/qmgr[9319]: F030911C008: removed
Apr 21 02:49:56 vps12345 postfix/smtp[9414]: F030911C008:
to=mailman-requ...@domain.org, relay=127.0.0.1[127.0.0.1]:10024,
delay=0.73, delays=0.26/0.01/0/0.46, dsn=2.0.0, status=sent (250 2.0.0 from
MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 9F72D11C00A)
Apr 21 02:49:56 vps12345 postfix/smtpd[9419]: disconnect from
localhost.localdomain[127.0.0.1]
Apr 21 02:49:56 vps12345 dovecot: auth: sql(mailman-requ...@domain.org):
Unknown user
Apr 21 02:49:56 vps12345 postfix/pipe[9420]: 9F72D11C00A:
to=mailman-requ...@domain.org, relay=dovecot, delay=0.04,
delays=0.01/0.01/0/0.02, dsn=5.1.1, status=bounced (user unknown)
Apr 21 02:49:56 vps12345 postfix/cleanup[9412]: A866A11C00B:
message-id=20140421004956.a866a11c...@vps12345.ovh.net
Apr 21 02:49:56 vps12345 postfix/qmgr[9319]: A866A11C00B: from=,
size=3206, nrcpt=1 (queue active)
Apr 21 02:49:56 vps12345 postfix/bounce[9422]: 9F72D11C00A: sender
non-delivery notification: A866A11C00B
Apr 21 02:49:56 vps12345 postfix/qmgr[9319]: 9F72D11C00A: removed
Apr 21 02:49:56 vps12345 dovecot: dict: mysql: Connected to localhost (mail)
Apr 21 02:49:56 vps12345 dovecot: lda(j.set...@domain.net): sieve:
msgid=20140421004956.a866a11c...@vps12345.ovh.net: stored mail into
mailbox 'INBOX'
Apr 21 02:49:56 vps12345 postfix/pipe[9420]: A866A11C00B:
to=j.set...@domain.net, relay=dovecot, delay=0.04, delays=0.01/0/0/0.04,
dsn=2.0.0, status=sent (delivered via dovecot service)
Apr 21 02:49:56 vps12345 postfix/qmgr[9319]: A866A11C00B: removed
Apr 21 02:49:58 vps12345 postfix/smtpd[9396]: disconnect from
[details-removed*]
___
(*) Details removed from log excerpt for privacy reasons.
2) Postfix 'transport' file content
___
[root@vps12345 ~]# postmap -s /etc/postfix/transport
autoreply.vps12345.ovh.net vacation:
[root@vps12345 ~]#
___
Does the above data details clarify in any way the previously reported issue
?
Jacques Setton
jset...@waycast.com
-Message d'origine-
De : Mark Sapiro [mailto:m...@msapiro.net]
Envoyé : vendredi 25 avril 2014 00:55
À : Jacques Setton
Cc : mailman-users@python.org
Objet : Re: [Mailman-Users] 'Undelivered Mail Returned to Sender' error when
using an e-mail from a domain co-hosted with the one used for Mailman lists
On 04/24/2014 02:56 PM, Jacques Setton wrote:
The complete output generated by the '# postconf -n' command is
appended below.
Besides that, I have not configured postfix in any
Re: [Mailman-Users] 'Undelivered Mail Returned to Sender' error when using an e-mail from a domain co-hosted with the one used for Mailman lists
On 04/25/2014 03:25 AM, Jacques Setton wrote: 1) Selected Sequence from /var/log/maillog ... Apr 21 02:49:56 vps12345 postfix/smtp[9414]: F030911C008: to=mailman-requ...@domain.org, relay=127.0.0.1[127.0.0.1]:10024, delay=0.73, delays=0.26/0.01/0/0.46, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 9F72D11C00A) Apr 21 02:49:56 vps12345 postfix/smtpd[9419]: disconnect from localhost.localdomain[127.0.0.1] Apr 21 02:49:56 vps12345 dovecot: auth: sql(mailman-requ...@domain.org): Unknown user Apr 21 02:49:56 vps12345 postfix/pipe[9420]: 9F72D11C00A: to=mailman-requ...@domain.org, relay=dovecot, delay=0.04, delays=0.01/0.01/0/0.02, dsn=5.1.1, status=bounced (user unknown) Delivery to Mailman is via aliases. The dovecot LDA does not use your aliases. Delivery to Mailman must be via the local LDA. Something in your Postfix configuration is telling it to relay this particular mail via the dovecot transport rather than the local transport. That's why it bounces. The question is what's causing it. I suspect it has to do with two things in your Postfix configuration: local_recipient_maps = unix:passwd.byname and virtual_transport = dovecot By default, local_recipient_maps includes $alias_maps, and I *think* it should in your case. Why this lack would cause Postfix to use the virtual_transport rather than local in just this one case is really a question for postfix-us...@postfix.org or some other Postfix resource, but you might try local_recipient_maps = unix:passwd.byname $alias_maps or simply removing that line from main.cf and see if that helps. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] 'Undelivered Mail Returned to Sender' error when using an e-mail from a domain co-hosted with the one used for Mailman lists
What's the rest of postconf -n? See http://www.list.org/mailman-install/postfix-integration.html and http://www.list.org/mailman-install/postfix-virtual.html. Have you configured Postfix this way or some other way ? The complete output generated by the '# postconf -n' command is appended below. Besides that, I have not configured postfix in any particular way... As previously indicated, Mailman works well with any external Email address, but not with the ones co-hosted on the same physical server... Any idea about what the problem could be ? Jacques Setton jset...@waycast.com COMPLETE OUTPUT OF POSTCONF -N COMMAND __ alias_database = hash:/etc/aliases, hash:/etc/mailman/aliases alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level = 2 html_directory = no inet_interfaces = all inet_protocols = all local_recipient_maps = unix:passwd.byname mail_owner = postfix mailbox_command = /usr/libexec/dovecot/deliver mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man milter_default_action = accept mydestination = localhost.$mydomain, localhost, localhost.localdomain mydomain = localdomain myhostname = vps39345.ovh.net mynetworks = 127.0.0.0/8 myorigin = $mydomain newaliases_path = /usr/bin/newaliases.postfix non_smtpd_milters = inet:localhost:8891 queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/postfix-2.6.6/README_FILES recipient_delimiter = + sample_directory = /usr/share/doc/postfix-2.6.6/samples sender_canonical_maps = hash:/etc/postfix/sender_canonical sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop smtpd_milters = inet:localhost:8891 smtpd_recipient_restrictions = check_recipient_access mysql:/etc/postfix/sql/mysql_amavis_in.cf, permit_mynetworks, reject_unauth_destination smtpd_tls_auth_only = yes smtpd_tls_cert_file = /etc/pki/tls/certs/localhost.crt smtpd_tls_key_file = /etc/pki/tls/private/localhost.key smtpd_tls_loglevel = 1 smtpd_tls_security_level = may smtpd_tls_session_cache_database = btree:/var/lib/postfix/smtpd_tls_cache.db smtpd_tls_session_cache_timeout = 3600s tls_random_source = dev:/dev/urandom transport_maps = hash:/etc/postfix/transport unknown_local_recipient_reject_code = 550 virtual_alias_maps = mysql:/etc/postfix/sql/mysql_virtual_alias_maps.cf, mysql:/etc/postfix/sql/mysql_virtual_alias_domain_maps.cf, mysql:/etc/postfix/sql/mysql_virtual_alias_domain_catchall_maps.cf, mysql:/etc/postfix/sql/mysql_virtual_mailing.cf, hash:/etc/mailman/virtual-mailman virtual_gid_maps = static:101 virtual_mailbox_base = /var/mail/vhosts virtual_mailbox_domains = mysql:/etc/postfix/sql/mysql_virtual_domains_maps.cf virtual_mailbox_maps = mysql:/etc/postfix/sql/mysql_virtual_mailbox_maps.cf, mysql:/etc/postfix/sql/mysql_virtual_alias_domain_mailbox_maps.cf virtual_transport = dovecot virtual_uid_maps = static:500 -Message d'origine- De : Mark Sapiro [mailto:m...@msapiro.net] Envoyé : jeudi 24 avril 2014 07:20 À : mailman-users@python.org Objet : Re: [Mailman-Users] 'Undelivered Mail Returned to Sender' error when using an e-mail from a domain co-hosted with the one used for Mailman lists On 04/23/2014 10:01 PM, Mark Sapiro wrote: Is the problem perhaps that the address in the confirmation should be mailman-requ...@domain.net instead of mailman-requ...@domain.org?. If so, see the FAQ at http://wiki.list.org/x/mIA9. Or maybe just set the host_name attribute on the list's General Options page to domain.net. Ignore the above portion of my prior reply. I wasn't paying enough attention to what the actual issue was. OK - JSetton -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] 'Undelivered Mail Returned to Sender' error when using an e-mail from a domain co-hosted with the one used for Mailman lists
On 04/24/2014 02:56 PM, Jacques Setton wrote: The complete output generated by the '# postconf -n' command is appended below. Besides that, I have not configured postfix in any particular way... As previously indicated, Mailman works well with any external Email address, but not with the ones co-hosted on the same physical server... Any idea about what the problem could be ? Not until you do as I asked before and post the resulting output from grepping the mail log for the Postfix queue id of a returned message. Based on your prior post, this would be something like grep 9F72D11C00A /var/log/maillog Also it might help to see your transport maps - /etc/postfix/transport -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] 'Undelivered Mail Returned to Sender' error when using an e-mail from a domain co-hosted with the one used for Mailman lists
On 04/21/2014 04:50 AM, Jacques Setton wrote: All mailman lists functions features work well on the later system except in one specific case. When I try to subscribe to a list (say ‘Mailman’) using an e-mail address based on a virtual domain (say ‘domain.net’) which is co-hosted with the default virtual domain used for Mailman lists (say ‘domain.org’), I immediately get an “Undelivered Mail Returned to Sender” error as depicted below : ... De : MAILER-DAEMON (Mail Delivery System) [mailto:MAILER-DAEMON (Mail Delivery System)] Envoyé : lundi 21 avril 2014 8:00 À : jset...@domain.net Objet : Undelivered Mail Returned to Sender This is the mail system at host vps12345.ovh.net. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system mailman-requ...@domain.org: user unknown Is the problem perhaps that the address in the confirmation should be mailman-requ...@domain.net instead of mailman-requ...@domain.org?. If so, see the FAQ at http://wiki.list.org/x/mIA9. Or maybe just set the host_name attribute on the list's General Options page to domain.net. Attached error file details Reporting-MTA: dns; vps12345.ovh.net X-Postfix-Queue-ID: 9F72D11C00A Post the results of grepping your maillog for 9F72D11C00A X-Postfix-Sender: rfc822; jset...@domain.net Arrival-Date: Mon, 21 Apr 2014 08:00:16 +0200 (CEST) Final-Recipient: rfc822; mailman-requ...@domain.org Original-Recipient: rfc822;mailman-requ...@domain.org Action: failed Status: 5.1.1 Diagnostic-Code: x-unix; user unknown - The 1st mail was sent to confirm the subscription to a list. The second mail is the response received in return, indicating that the mailman specified address was unknown. The attached error report follow thereafter. The collocated virtual domains labeled ‘domain.org’ and ‘domain.net’ are hosted on the same physical server ‘vps12...@ovh.net’, sharing a common IP address. Would such behavior be related to a bad or incomplete definition of the ‘mydestination’ / ‘myorigin’ parameters in the Postfix ‘main.cf’ file ? Probably not. It depends on how postfix is delivering to Mailman. Are you using aliases and virtual alias maps or some alternate transport? Here is an excerpt of the related values produced by the ‘postconf –n’ command line : What's the rest of postconf -n? See http://www.list.org/mailman-install/postfix-integration.html and http://www.list.org/mailman-install/postfix-virtual.html. Have you configured Postfix this way or some other way? -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] 'Undelivered Mail Returned to Sender' error when using an e-mail from a domain co-hosted with the one used for Mailman lists
On 04/23/2014 10:01 PM, Mark Sapiro wrote: Is the problem perhaps that the address in the confirmation should be mailman-requ...@domain.net instead of mailman-requ...@domain.org?. If so, see the FAQ at http://wiki.list.org/x/mIA9. Or maybe just set the host_name attribute on the list's General Options page to domain.net. Ignore the above portion of my prior reply. I wasn't paying enough attention to what the actual issue was. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Undelivered Mail Returned to Sender
Pablo Arturi wrote: I have just installed Mailman and I am getting an error everytime I send an email to the list. The error is: |/usr/local/mailman/mail/mailman post whb-ventas@bw-ip-34.dnsba.com (expanded from [EMAIL PROTECTED]): Host or domain name not found. Name service error for name=bw-ip-34.dnsba.com type=A: Host not found It appears that your MTA does not recognize pipes in the list aliases. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
