similar to: DSN: failed (Delivery failed)

This is a Delivery Status Notification (DSN). I was unable to deliver your message to email-virtue@mptmail.net.mm. I said RCPT TO:<email-virtue@mptmail.net.mm> And they gave me the error; 550 5.1.1 <email-virtue@mptmail.net.mm>... User unknown _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

This is a Delivery Status Notification (DSN). I was unable to deliver your message to vijayengg6@vsnl.net. I said RCPT TO:<vijayengg6@vsnl.net> And they gave me the error; 550 5.1.1 unknown or illegal alias: vijayengg6@vsnl.net _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

This is a Delivery Status Notification (DSN). I was unable to deliver your message to swamycottonmill@vsnl.net. I said RCPT TO:<swamycottonmill@vsnl.net> And they gave me the error; 550 5.1.1 unknown or illegal alias: swamycottonmill@vsnl.net _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

This is a Delivery Status Notification (DSN). I was unable to deliver your message to vous@corse.tk. I said RCPT TO:<vous@corse.tk> And they gave me the error; 554 5.1.2 <vous@corse.tk>: Recipient address rejected: Bad destination system address _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

This is a Delivery Status Notification (DSN). I was unable to deliver your message to whereabouts@radaris.com. I said RCPT TO:<whereabouts@radaris.com> And they gave me the error; 550 5.1.1 <whereabouts@radaris.com>: Recipient address rejected: User unknown in virtual mailbox table _______________________________________________ Xen-users mailing list

On 12/03/2020 08:04, Jean-Daniel wrote: > > >> Le 11 mars 2020 ? 19:32, Juri Haberland <juri at koschikode.com> a ?crit : >> >> Hi list, >> >> I have a small problem with recipient_delimiters contained in usernames. >> Recently I have extended recipient_delimiter from "+" to "+-" in both >> Postfix and Dovecot (using

Hi list, I am running a Debian Lenny machine with Postfix 2.5.5 and Dovecot 2.0.8. Up until now I ran Postfix with the Procmail delivery agent succesfully. The machine has only local users; I am not using virtual mailboxes. Due to obvious reasons I want to switch to Dovecot LDA delivery, through LMTP. I spend quite some time finding 'the' configuration for both Postfix and Dovecot,

This is a Delivery Status Notification (DSN). I was unable to deliver your message to hartutil@hiwaay.net. I said RCPT TO:<hartutil@hiwaay.net> And they gave me the error; 550 5.7.1 <hartutil@hiwaay.net>: Recipient address rejected: hartutil@hiwaay.net doesn''t accept mail _______________________________________________ Xen-users mailing list

This is a Delivery Status Notification (DSN). I was unable to deliver your message to zhangnd@163.net. I said RCPT TO:<zhangnd@163.net> And they gave me the error; 550 <zhangnd@163.net>: Invalid User _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I briefly got some mails delivered, but not anymore. Attached are dovecot-info.log, dovecot-debug.log, dovecot.log, maillog, /etc/mail/passwd smtpd.conf, vaddr, vusers, vdomains Thanks for any help. Chris Bennett -------------- next part -------------- May 15 12:54:25 master: Error: service(config): pipe() failed: Too many open files May 15 12:54:25 master: Error: service(auth): pipe() failed:

On 04.03.2018 16:25, Reio Remma wrote: > Hello! > > I'm having crashes with LMTP delivery when user is over quota on the > latest CentOS 7.4 with the latest Dovecot 2.3.0.1 from Dovecot repo. > > I see the issue has been fixed on January 17, but it doesn't seem to > have made it into 2.3.0.1 (I compared with the source from >

Hello: CentOS 5.2 Postfix 2.3.3 + updates (bundled with CentOS 5.2) Dovecot-1.0.7 (bundled with CentOS 5.2) Dovecot-1.1.1 (Updated from www.atrpms.com) Dovecot-sieve-1.1.5 (Updated from www.atrpms.com) During the last few days I have installed dovecot many times without errors. Today I installed dovecot-1.1.1 & sent a test message to 'test at tib.com'. I received the following

This is a Delivery Status Notification (DSN). I was unable to deliver your message to andyc@apache.org. I said (end of message) And they gave me the error; 552 CMD attachments are not accepted here. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi Everyone, I thought I'd try asking here before joining the postfix mail list since I'm running postfix on a CentOS 7 box. I want to look up accounts via LDAP (an IPA server also on CentOS 7). I created an "ldap_aliases" file and successfully tested it with the postmap command: I can get the email address for an arbitrary user. But, when I add the very same file to main.cf, I

****** Message from InterScan E-Mail VirusWall NT ****** Sent >>> RCPT TO: <mg@unipress.com> Received <<< 550 5.1.1 <mg@unipress.com>... User unknown Could not deliver mail to this user. mg@unipress.com ***************** End of message ***************

Oh wait, you crossposted to the postfix list. Please keep the discussion there going, you have a postfix issue, not a dovecot one ;) Tom On 02-03-17 09:40, Tom Hendrikx wrote: > Hi, > > Typically, postfix should resolve the aliases into user accounts that > dovecot knows before you even start delivering to dovecot. You probably > messed something up in the postfix config that

Recently configured postfix to use the dovecot lda as I wanted to use sieve. Got that working a few days ago but noticed that I wasn't getting any emails to aliases. Checked the logs and saw messages like: Mar 1 08:19:59 carson postfix/lmtp[16949]: 0DCD22016BE: to=< sales at example.com>, relay=carson.example.com[private/dovecot-lmtp], delay=0.07, delays=0.01/0.01/0/0.04, dsn=5.1.1,

Hi all, I?ve got postfix setup to use dovecot-lmtp for (virtual) user delivery, and things to users or aliases that Dovecot knows about now get delivered correctly. However, I?ve done something wrong with postfix and/or the LMTP configuration because upon RCPT TO, instead of forwarding the mail off to the configured smartest, somehow dovecot-lmtp is ending up in the mix. (Perhaps this is more a

Hi, Typically, postfix should resolve the aliases into user accounts that dovecot knows before you even start delivering to dovecot. You probably messed something up in the postfix config that disables alias expansion before dovecot delivery is attempted. Can you show us your postfix config? Kind regards, Tom On 01-03-17 15:36, Ian Evans wrote: > Recently configured postfix to use the

For archiving purposes I'm delivering all addresses to the same mdbox: like this: passdb { driver = passwd-file args = username_format=%u /etc/dovecot/passwd } userdb { driver = static args = uid=1000 gid=1000 home=/home/copymail allow_all_users=yes } Yet I'm getting this: Jan 3 19:03:27 mail postfix/lmtp[29378]: 3THjg02wfWzFvmL: to=<firstname.lastname at