gmane.mail.postfix.user

Re: Postfix and Dovecot missing delivery

jeffrey j donovan — 2012-05-26T00:55:47

On May 25, 2012, at 4:06 PM, Jan Meyland Andersen wrote:




i don't see a " mailbox_command =  "
I have a debian system here, this is how I get mail delivered to local/user/inbox

mailbox_command = /usr/lib/dovecot/deliver -c /etc/dovecot/conf.d/01-mail-stack-delivery.conf -m "${EXTENSION}"

postconf -d # see system default
postconf -n # see what you configured.
gl
-j

Re: Postfix and Dovecot missing delivery

Noel Jones — 2012-05-25T22:20:18

[guess you missed the part about not top-posting]

On 5/25/2012 4:58 PM, Jan Meyland Andersen wrote:


To "empty" /var/spool/mail/jan, just rm it.

If you need to save those messages, you'll need to find some other
utility that will read it.  It *should* be a "mailbox" type file, so
mb2md ought to read it.  Maybe try a different tool, or find out why
mb2md doesn't like your command.

Sounds like the postfix part is working; good luck with the rest of it.


  -- Noel Jones

Re: Postfix and Dovecot missing delivery

Jan Meyland Andersen — 2012-05-25T21:58:46

Hi Noel

Thanks. Now it works perfectly.

But how do I empty the /var/spool/mail file that was generated earlier.

I tried to run a mb2md on it but it says it is not a mailbox.

Kind Regards

Jan Andersen


On Fri, May 25, 2012 at 11:38 PM, Noel Jones <njones< at >megan.vbhcs.org> wrote:

Re: Postfix and Dovecot missing delivery

Noel Jones — 2012-05-25T21:38:44

[please don't top post]

For a virtual mailbox domain, the domain must NOT be listed in
mydestination, and must be listed in virtual_mailbox_domains.
http://www.postfix.org/VIRTUAL_README.html#virtual_mailbox

If you already have it listed in your virtual_mailbox_domains map,
removing it from mydestination might be all that's needed.



  -- Noel Jones

Re: postmaster required / close port 25

/dev/rob0 — 2012-05-25T21:24:43

This is proper.


cleanup(8) is never the first logging for a message received; it 
would be either pickup(8) or smtpd(8). But no matter. You did 
describe the issue well enough.


Your provider doesn't want to accept these bounces, for whatever 
reason they might have. Yes, their rejection message is wrong.


If you're only sending these bounces to your own address[es], you are 
not a backscatterer. If you're sending bounces everywhere, you might 
be. From what you have said here, I doubt it is backscatter.

Perhaps you want to use another sender domain, one you control and 
host, to receive your bounces. Or, as suggested upthread, consult 
with the provider about their policy.

Re: Postfix and Dovecot missing delivery

Jan Meyland Andersen — 2012-05-25T21:21:15

Hi Noel

Thanks a lot. The mails was there.

I can see a lot of info in the link supplied but still can't find out
what to do to solve this?
What do I need to change?
I want virtual domains and therefore should be able to receive mails
for users without a username for the system.


Kind Regards

Jan


On Fri, May 25, 2012 at 10:56 PM, Noel Jones <njones< at >megan.vbhcs.org> wrote:

Re: Postfix SMTP Client Segfaults over TLS

Wietse Venema — 2012-05-25T21:15:50

Daniel Sutcliffe:

Was Postfix compiled for openssl 1.0.0? If it was built for 0.9.mumble,
then the warranty is void and all bets are off.

Wietse

Re: Subdomain users through my smtpd_sender_restrictions

Reindl Harald — 2012-05-25T21:14:50


Am 25.05.2012 21:08, schrieb Carlos R Laguna:

i do dot understand you text

BUT the part "Subdomain users" of the subject seems
you are not aware that a subdomain in case of mailservers
has to be configured like each other domain

to make it clear: ayn configuration for "example.com" has no
effect to "subdomain.example.com", you have to configure
"subdomain.example.com" at its own

Re: Rejecting based on message/partial

Noel Jones — 2012-05-25T21:08:33

I don't know of any malware that uses message/partial, but it's
still true that partial messages cannot be effectively scanned by
the MTA.


There is no bypass mechanism for header_checks.  If someone must
send you message/partial content, they will either need to use an
alternate channel or you'll need to remove that check (or use HOLD
for manual inspection rather than REJECT).

I would personally judge the risk as fairly low, but you'll need to
decide that for yourself.


  -- Noel Jones

Re: Postfix and Dovecot missing delivery

Noel Jones — 2012-05-25T20:56:37

[post plain text only; the html markup makes the logs harder to read]

Looks as if you're trying to use dovecot as the delivery agent for
virtual mailbox domains, and your domain is set as a local domain
(the is domain listed in mydestination; delivery is by the postfix
"local" delivery agent).  You'll probably find the previously
delivered mail in /var/mail or /var/spool/mail.
http://www.postfix.org/ADDRESS_CLASS_README.html
http://www.postfix.org/local.8.html
http://www.postfix.org/VIRTUAL_README.html#virtual_mailbox



  -- Noel Jones

Re: Subdomain users through my smtpd_sender_restrictions

Noel Jones — 2012-05-25T20:39:45


It is unclear what you're referring to.  Postfix applies all
smtpd_*_restrictions to all mail, with clients listed in $mynetworks
getting special treatment.
http://www.postfix.org/BASIC_CONFIGURATION_README.html
http://www.postfix.org/SMTPD_ACCESS_README.html

Perhaps you need to add some internal servers to mynetworks?

Please show your "postconf -n" output and postfix logs of the
unwanted behavior, along with your description of what you expected
to happen.
http://www.postfix.org/DEBUG_README.html#mail



  -- Noel Jones

Re: Postfix SMTP Client Segfaults over TLS

Daniel Sutcliffe — 2012-05-25T20:23:35

I'm having a very similar problem here on CentOS 6 - unfortunately moving or
removing the TLS session caches and restarting postfix is not fixing my problem
at all.  Coincidently the openssl package was updated the day before the problem
started.
  postfix 2.6.6-2.2.el6_1
  openssl 1.0.0-20.el6_2.4

postconf: http://pastebin.com/d898xtus

maillog (with -v on smtp line in master.cf): 
  May 25 20:20:17 li postfix/smtp[17618]: < smtp.gmail.com[173.194.77.108]:587:
250-mx.google.com at your service, [72.3.189.225]
  May 25 20:20:17 li postfix/smtp[17618]: < smtp.gmail.com[173.194.77.108]:587:
250-SIZE 35882577
  May 25 20:20:17 li postfix/smtp[17618]: < smtp.gmail.com[173.194.77.108]:587:
250-8BITMIME
  May 25 20:20:17 li postfix/smtp[17618]: < smtp.gmail.com[173.194.77.108]:587:
250-STARTTLS
  May 25 20:20:17 li postfix/smtp[17618]: < smtp.gmail.com[173.194.77.108]:587:
250 ENHANCEDSTATUSCODES
  May 25 20:20:17 li postfix/smtp[17618]: server features: 0x101b size 35882577
  May 25 20:20:17 li postfix/smtp[1761

Rejecting based on message/partial

Alex — 2012-05-25T20:16:59

Hi,

I have a header check that I added some time ago that rejects mail
with message/partial content type because I believe it can't be
scanned for potential viruses unless it is first assembled:

/^(Content-(Disposition|Type)\:|[[:space:]]+).*message\/partial.*;?$/
REJECT This mail server does not permit messages with 'Content-type:
message/partial'.

Does this still present a significant threat these days, or is it okay
to permit partial messages?

If I were to permit it for a specific IP address or sender, would that
be done in a check_sender_access hash?

smtpd_recipient_restrictions =
        ...
        check_client_access hash:/etc/postfix/client_checks,
        check_sender_access hash:/etc/postfix/sender_checks,

/etc/postfix/sender_checks:
   63.87.XX.0/25                   OK

Thanks,
Alex

Subdomain users through my smtpd_sender_restrictions

Carlos R Laguna — 2012-05-25T19:08:25

Hello everyone i am facing a big mess here i had my MTA whith my own
user but this server is also a relay server for several subdomain the 
problem is that my own politic are been aplied to user that arent my, 
any clue why this is happening . Regards

Postfix and Dovecot missing delivery

Jan Meyland Andersen — 2012-05-25T20:06:42

Hi

I have a problem with the delivery of mails using dovecot as a transport.
According to the logfile mails seems to be delivered but nothing ends up in
the maildir.

my main.cf is the following.

smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no
append_dot_mydomain = no
readme_directory = no
smtpd_use_tls=yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
smtpd_tls_cert_file = /etc/postfix/smtpd.cert
smtpd_tls_key_file = /etc/postfix/smtpd.key
smtpd_tls_security_level = may
smtpd_tls_received_header = no
smtpd_tls_loglevel = 0
tls_random_source = dev:/dev/urandom
virtual_mailbox_maps = mysql:/etc/postfix/mysql/aliases.cf
virtual_alias_maps = mysql:/etc/postfix/mysql/remote_aliases.cf
virtual_uid_maps = mysql:/etc/postfix/mysql/vuids.cf
virtual_gid_maps = mysql:/etc/postfix/mysql/vgids.cf
virtual_mailbox_base = /var/spool/postfix/virtual
virtual_mailbox_limit = 102400000
virtual_alias_domains =
vi

Re: smtp sasl client strange behavior?

Wietse Venema — 2012-05-25T18:51:04

Matt Teagarden:

Show logs and "postconf -n" command output for TWO cases: one that
does work, and one that doesn't work as expected.

Wietse

smtp sasl client strange behavior?

Matt Teagarden — 2012-05-25T18:34:50

I am working on having a postfix server relay certain messages via 
another server instead of delivering normally.  My issue that I can't 
figure out is  trying to get postfix to authenticate with another mail 
server (no tls).  If the other server is listening on seemingly any 
other port than 25,   the auth works normally and the message goes 
thru.  When postfix trys to send to a relay host on port 25 though,  it 
never even tries to authenticate and relaying fails.    I am working 
with postfix 2.3.3 on centos 5.7 BTW.    (both machines in play here are 
vm's so I won't mask any of the config)

The server I am sending to (under my control) always replies to an ehlo 
the same way (no matter what port I tell it to listen on) with:

Escape character is '^]'.
220 test.test
ehlo sdfgsdfg
250-test.test
250-PIPELINING
250-SIZE 30240000
250-ETRN
250-STARTTLS
250-AUTH PLAIN LOGIN
250-AUTH=PLAIN LOGIN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN


Postfix Config:  (the one that needs to relay to another machine)
r

Re: Cannot make "smtpd_sender_restrictions = check_sender_access" work properly‏

Noel Jones — 2012-05-25T18:05:53

Requested information for assistance is described in the list
welcome message and here:
http://www.postfix.org/DEBUG_README.html#mail



Is this how the actual user submits mail, or is this just for testing?


This mail was submitted via the sendmail(1) command.  Only mail
submitted via SMTP is subject to the smtpd_*_restrictions.

Maybe this is what you're looking for
http://www.postfix.org/postconf.5.html#authorized_submit_users


  -- Noel Jones

Re: Cannot make "smtpd_sender_restrictions = check_sender_access" work properly‏

Brian Evans - Postfix List — 2012-05-25T18:02:26

Please do not post or enable verbose logging unless asked.  It generally
masks the real issue.


This mail entered via the pickup service (aka via the sendmail(1) command).
smtpd_sender_restrictions will never apply to anything except mail
received through smtpd.

Brian

Re: postmaster required / close port 25

Reindl Harald — 2012-05-25T17:42:21


Am 25.05.2012 19:37, schrieb Charles Marcus:

and they are playing spammers in their hand

i am seeing here around 50000 spam-mails to non-existent
RCPT in valid domains - if there would be catch-all we
would have two problems

the second only in the worst case they pass the spam-firewall

* 200 OK to the spammer which feels sucess and earn money
* 1.5 Mio messages to store and backup each month

Re: postmaster required / close port 25

Charles Marcus — 2012-05-25T17:37:39

Please do NOT use catch-all addresses, as that breaks recipient 
validation... anyone who sends an email to one of your users and typos 
their address will not know it...

Catch-alls are *always* a very bad idea, except in very specific special 
use cases...